Object Editors

Previous  Top  Next

In order to create and alter your database objects like Tables, Views, Triggers etc, Database Workbench has specialized Object Editors (more information about each type of editor can be found here). These editors can be reached via the Editors toolbar, or the main menu Editors | <object editor name>, or the Database Navigator by double clicking (or the context menu) any object or double clicking any object folder (like Tables) in the treeview.


The Editors Toolbar


The small arrows besides the buttons let you select a previously opened editor. The current active editor is shown in bold in these menus. The default action of the buttons is to create a new object editor.


All object editors have a similar layout:


Example Object Editor - in this case, an InterBase Trigger Editor


All object-editors have the "object selection" drop down boxes that list all objects (of a type the editor understands) in your database. In the above example, you can see that Triggers are "sub-objects" of tables and views. In the case of sub-objects, you have two selection boxes and the first one always lists the "parent-objects" like Tables.


There's also a toolbar with several buttons - the minimum amount of buttons is always a New, Create/Alter, Drop and Extract DDL button. The New button creates a new object for you, that won't be saved into your database until you use the Create/Alter button. That goes for any change - nothing will be saved unless you tell Database Workbench to do so.


Next, all editors have at least 1 tab with the object details.


For objects and database engines that support it, Database Workbench also has a tab called Description where you can view and edit a user written descripton of the object.


Each editor has a tab called DDL that holds the metadata statement(s) to create and alter the object (after changes have been made). You can copy the statement from here if you like.


If the object and database engine supports it, the editor also has a tab Dependencies listing any other database objects that explicitly depend on this object to exist.


Example Dependencies tab for a Stored Procedure


As you can see in the above screenshot, this procedures depends on another stored procedure GET_VERKOOPPRIJS and a table called PRIJSLIJSTREGEL - especially on columns INKOOPPRIJS, PRIJSLIJSTREGELID etc...