The "Context" is the set of operations you can use for the selected object in the object tree browser. You can use the alternative access to this menu by clicking the right mouse button on an item in the shema browser (for right handed mouse).
The context menu only shows operations which are available for the selected database object: if there isn't one, the menu is disabled.
Force a refresh of the schema browser. Sqliteman should handle user changes in the schema automatically but you can use this option to update the browser to show changes made outside sqliteman
Disconnect an attached database from the current session. See full Attach Database documentation.
Raise a dialog for table creation. You can use three ways to create a table here. See full Create Table documentation .
Show in the script output database schema information for the selected table.
Raise a dialog to modify a table. This allows some more general changes than the built-in sqlite ALTER TABLE statement, but does not handle some special cases. See full Alter Table documentation.
Drop the table (remove it from the database). Sqliteman will ask if you really want to do this.
Delete all records but keep the table: this is shown only if the table contains some records. Sqliteman will ask if you really want to do this.
Raise a dialog to build and execute a simple query on the selected table or view. See full Query Builder documentation .
Raise a dialog to import data into table. See full Import Table Data documentation .
Raise a dialog to create table content, for testing etc. See full Populate Table documentation.
Raise a dialog to create a view. See full Create View documentation.
Show in the script output database schema information for the selected view.
Raise a dialog to redefine an existing view rather than creating a new one. Currently this dialog only allows you to edit the SQL code to create the view. Since sqlite has no ALTER VIEW statement, altering a view is implemented by dropping the view and creating a new one. This is done within a transaction in order to prevent the view being lost if you get the SQL code wrong.
Drop the view (delete it from the database). Sqliteman will ask if you really want to do this.
Perform REINDEX command. If is it called when an index is selected, only that index is recreated. If is it called when a table is selected all indexes on that table are recreated.
Raise a dialog to create a new index. See full Create Index documentation.
Show in the script output database schema information for the selected index.
Drop the index (delete it from the database). Sqliteman will ask if you really want to do this.
Raise a dialog to create a new trigger. There is a trigger template prepared for you. Just modify it to your needs. Then press the "Create" button and check the result.
Raise a similar dialog to the "Create Trigger" one with current trigger body preset. Sqlite does not support direct ALTER TRIGGER so there is a DROP and new CREATE performed after you click the button. This is done within a transaction in order to prevent the trigger being lost if you get the SQL code wrong.
Drop the trigger (delete it from the database). Sqliteman will ask if you really want to do this.
Show database schema information for the trigger in the script result window.
Raise a dialog to create FOREIGN KEY constraint checks in the triggers. See full Constraint Triggers documentation .