The Preferences dialog allows you to customize sqliteman to fit your needs better.
Any changes to preferences are not stored until and unless you click on the button. If you click on the button or dismiss the window, your changes will not be stored.
You can set GUI behavior in in this section. Remember that Language and Style settings only take effect when sqliteman is restarted. Some of these preferences can be overridden by the application command line parameters.
- GUI Language
-
Allows you to choose one of the translations for the user interface.
Caution
Remember that translations are provided by a group of volunteers (not by the sqliteman developers). It's better to contact translation authors in the case of any errors.
In this version, translations are not currently being updated. Volunteers to update them are welcome.
Change the application "skin". Available styles depend on what is installed on your platform. The default style should be a good choice.
Change the font and/or size used for GUI text.
Specify the number of items in the File->Recent Databases menu.
If this box is checked, the last used database will be opened when sqliteman starts.
If this box is checked, the last used SQL script will be opened when sqliteman starts.
This determines the number of rows initially read from a table when opening it. Available choices are 256, 512, 1024, 2048, 4096, or All. Unless your computer is slow or short of memory or you are opening big databases, "All" is usually the best choice
If this box is checked, clicking the New Row or Duplicate Row button will cause the newly created row to be opened in the Item View.
If this box is not checked, all fields of a new row will be NULL, and all fields of a copy row will be exact copies of the copied row. This means that sqliteman does not show you what will actually be inserted when you commit the new or copied row into the database, and committing changes may cause uniqueness constraint violations. Additionally sqlite allows a field with a UNIQUE constraint or which is a PRIMARY KEY (which implies a UNIQUE constraint) to be NULL in multiple rows without violating the constraint. This behaviour is supported by sqliteman for legacy compatibility reasons and is probably not what you want when creating a new row.
If this box is checked, when creating a new row sqliteman will insert default values. For both new and copied rows, sqliteman will calculate a value for any field which is an INTEGER PRIMARY KEY (but not DECR) alias for the rowid, force an empty string into any field which would otherwise violate a NOT NULL constraint, and overwrite default or copied values if necessary to make UNIQUE fields and the first or only PRIMARY KEY field unique and not NULL.
It is not possible for sqliteman to insert exactly what sqlite would insert. In order to display default values sqliteman must calculate them when a new row is created, not when it is committed into the database, so timestamps may be earlier and default expressions involving sqlite built-in functions can produce different values at different times. Rowid aliases can also differ if some other process inserts or deletes rows, or if the maximum possible rowid number (9223372036854775807) has been used. If another process inserts rows, uniqueness contraints can still be violated when you commit your changes.
You can change the settings of the Data Viewer here. Changes take effect immediately with no need for a restart. Viewer features are described in its own section.
- NULL handling
-
If NULL highlighting is enabled, you can set a text string to be displayed in a NULL field and the background colour.
If NULL highlighting is not enabled, there is no visible difference between a NULL value and an empty string, although sqlite treats them differently.
- BLOB handling
-
If BLOB highlighting is enabled, you can set a text string to be displayed in a BLOB field and the background colour.
If BLOB highlighting is not enabled, you will get the unfiltered binary content of a BLOB cell.
- Limit Text Length Display
-
If this box is checked, when showing the Full View of a table or the result of a query, the Data Viewer will truncate field values instead of trying to expand the widths of the columns or breaking the text over multiple lines.
You can change settings of the SQL editor here. Changes take effect immediately without needing a restart of sqliteman. SQL Editor features are described in its own section.
- Font
-
Specify font and font size. It is usual to use a non-proportional font for the source code editor.
- Use Active Line Highlightin
-
The active line will be highlighted if this feature is set. Change the highlight background colour with the button.
- Use Maximum Text Width Mark
-
When this option is set, a vertical line at the given column position will be shown. This can be useful to keep coding standards
- Use Code Completion With Length
-
Code completion will be enabled if is this feature is set. The editor will show a pop-up menu with matching words when the currently edited word reaches the threshold length.
- Use Editor Shortcuts
-
The editor shortcuts mechanism will be allowed if this feature is enabled. Pressing the button will open a shortcut definition dialog.
You can define shortcuts and expansion in this sub-dialog:
Here you can enable or disable extension loading and add or remove sqlite extensions from the list of those automatically loaded when sqliteman is started. Extensions can also be explicitly loaded from the Menu.
- Allow Extension Loading
-
If the box is checked, extension loading is allowed.
- Automatically Loaded Extensions
-
The list shows the extensions which will be automatically loaded when sqliteman is started. The button will bring up a file browser window to add an extension to the list. Selecting an extension in the list (by clicking on it) and then clicking the button will remove the selected extension from the list.