License) and the IDPL (Initial Developer's Public License). The first one covers the parts of the source code that were inherited from InterBase; the second applies to the additions and improvements made by the notices included with Firebird must remain intact. • You may modify and recompile the Firebird source code or parts of it. You may distribute such modified versions, but if you do so, you must document your make them publicly available, at no cost, under the same license as the original code. • You may include Firebird source code (modified or not) in a larger work and distribute that larger work, in source

.............................................................................. 3 3. Zumero tables vs. regular SQLite tables ........................................................................... you normally would. (A complete explanation of the differences appears in Chapter 3, Zumero tables vs. regular SQLite tables). The rest of this document is filled with all kinds of other information we stopped reading now, you and Zumero could still get a lot of work done . 4 Chapter 3. Zumero tables vs. regular SQLite tables Zumero tables are implemented as SQLite virtual tables1. This is the same mechanism

Disabled if the SQL code is read-only Save to file Allows saving the current SQL code to a file Open in SQL console Opens the SQL code in an SQL Editor You can select parts of the SQL code and apply generic commands like formatting – using the context menu. To open the context menu, right-click the SQL code. See for information about SQL-specific commands. SQL Editor NOTE: , , and menu items on the appear as rows, and rows hide in one column, see details in the section of article. Value Table vs. Record Views The bottom toolbar provides the following buttons: Button Name Description Save Saves

Disabled if the SQL code is read-only Save to file Allows saving the current SQL code to a file Open in SQL console Opens the SQL code in an SQL Editor You can select parts of the SQL code and apply generic commands like formatting – using the context menu. To open the context menu, right-click the SQL code. See for information about SQL-specific commands. SQL Editor NOTE: , , and menu items on the appear as rows, and rows hide in one column, see details in the section of article. Value Table vs. Record Views The bottom toolbar provides the following buttons: Button Name Description Save Saves

Disabled if the SQL code is read-only Save to file Allows saving the current SQL code to a file Open in SQL console Opens the SQL code in an SQL Editor You can select parts of the SQL code and apply generic commands like formatting – using the context menu. To open the context menu, right-click the SQL code. See for information about SQL-specific commands. SQL Editor NOTE: , , and menu items on the appear as rows, and rows hide in one column, see details in the section of article. Value Table vs. Record Views The bottom toolbar provides the following buttons: Button Name Description Save Saves

Disabled if the SQL code is read-only Save to file Allows saving the current SQL code to a file Open in SQL console Opens the SQL code in an SQL Editor You can select parts of the SQL code and apply generic commands like formatting – using the context menu. To open the context menu, right-click the SQL code. See for information about SQL-specific commands. SQL Editor NOTE: , , and menu items on the appear as rows, and rows hide in one column, see details in the section of article. Value Table vs. Record Views The bottom toolbar provides the following buttons: Button Name Description Save Saves

Disabled if the SQL code is read-only Save to file Allows saving the current SQL code to a file Open in SQL console Opens the SQL code in an SQL Editor You can select parts of the SQL code and apply generic commands like formatting – using the context menu. To open the context menu, right-click the SQL code. See for information about SQL-specific commands. SQL Editor NOTE: , , and menu items on the appear as rows, and rows hide in one column, see details in the section of article. Value Table vs. Record Views The bottom toolbar provides the following buttons: Button Name Description Save Saves

Disabled if the SQL code is read-only Save to file Allows saving the current SQL code to a file Open in SQL console Opens the SQL code in an SQL Editor You can select parts of the SQL code and apply generic commands like formatting – using the context menu. To open the context menu, right-click the SQL code. See for information about SQL-specific commands. SQL Editor NOTE: , , and menu items on the appear as rows, and rows hide in one column, see details in the section of article. Value Table vs. Record Views The bottom toolbar provides the following buttons: Button Name Description Save Saves

Disabled if the SQL code is read-only Save to file Allows saving the current SQL code to a file Open in SQL console Opens the SQL code in an SQL Editor You can select parts of the SQL code and apply generic commands like formatting – using the context menu. To open the context menu, right-click the SQL code. See for information about SQL-specific commands. SQL Editor NOTE: , , and menu items on the appear as rows, and rows hide in one column, see details in the section of article. Value Table vs. Record Views The bottom toolbar provides the following buttons: Button Name Description Save Saves

Disabled if the SQL code is read-only Save to file Allows saving the current SQL code to a file Open in SQL console Opens the SQL code in an SQL Editor You can select parts of the SQL code and apply generic commands like formatting – using the context menu. To open the context menu, right-click the SQL code. See for information about SQL-specific commands. SQL Editor NOTE: , , and menu items on the rows, and the rows hide in one column, see details in the section of the article. Value Table vs. Record Views The bottom toolbar provides the following buttons: Button Name Description Save Saves