All database objects are listed in this widget. Objects are grouped into a logical tree. Available actions for the chosen tree item (table, index, view etc.) are dynamically shown in the Context menu in the menu bar or in the pop-up menu (right mouse click on a tree item).
The Pragma Editor allows you to view database parameters, and change (most of) those which can be changed. Hovering the mouse over a pragma name in the Pragma Editor will show editable if the value is a single value which can be changed, or read-only if the value is a single value which can't be changed, or table if the value is a table. If the value column for a table does not show Not Set, the table will be displayed in a pop-up window if you click on the pragma name. If the value column for a table does show Not Set, this pragma requires a parameter. You can execute it with a paremeter by writing some SQL code in the SQL Editor,
The pragmas empty_result_callbacks and schema_version are allowed by the sqlite interface to be changed, but changing them would interfere with the operation of sqliteman, so the Pragma Editor does not allow you to change them. If you change them by executing code from the SQL Editor, the subsequent behaviour of sqliteman is unpredictable.
The pragmas incremental_vacuum, optimize, shrink_memory, and wal_checkpoint are executed for their side-effects, and do not store or return a value. They are not shown in the Pragma Editor because attempting to read a value from them would cause the side-effects.
The pragma case_sensitive_like cannot be read in the normal way, so sqliteman executes a bit of SQL code to determine its current value. The pragma encoding only affects the creation of new databases: if a database is currently open, sqlite ignores any attempt to change encoding. If an existing database is opened, the value of encoding is updated to reflect the encoding of that database. The pragma defer_foreign_keys only has effect if issued inside a transaction, and reverts to its default value (0) when the outermost transaction is rolled back or committed.
The Extensions Tab shows a list of currently loaded extensions. Additional extensions can be loaded from the system menu. The extensions to be loaded when sqliteman is started can be specified in the Extension manager in the Preferences dialog, itself reachable from the File Menu. Sqlite does not provide for an extension to be unloaded: to do that, you need to exit sqliteman and restart it.