The Table Editor dialog window is intended for editing the following properties of a diagram
table: general and database-specific table options (table name, etc.); table columns, table indexes, table constraints, table rules, display options and others.
To open Table Editor, simply double-click on a table in the diagram or select the
Properties item from the table context menu.
Table Editor consists of several tabs. please see the detailed description below.
This tab allows you to adjust the basic table properties, which are used for generating CREATE
TABLE or ALTER TABLE statements for executing on the PostgreSQL server.
The name of the table must be unique within the schema. To check your diagram for the
uniqueness of table names use the Check Diagram
The name of the schema where your table will be created.
This optional clause specifies whether the rows of your new table should have OIDs (object
identifiers) assigned to them.
A role which will be owner of the object, or a role which will execute CREATE script in case
of empty input field.
The name of a tablespace. A tablespace allows you to define an alternative location on the file
system where the data files containing database objects (such as tables and indexes) may reside. You can
manage tablespaces using SQL commands such as CREATE TABLESPACE and ALTER TABLESPACE.
This option allows you to create a temporary table, i.e. a table which drops itself at the end
of the session.
The fillfactor for a table is a percentage between 10 and 100. 100 (complete packing) is the
default. When a smaller fillfactor is specified, INSERT operations pack table pages only to the
indicated percentage; the remaining space on each page is reserved for updating rows on that page.
This gives UPDATE a chance to place the updated copy of a row on the same page as the original,
which is more efficient than placing it on a different page. For a table whose entries are never
updated, complete packing is the best choice, but in heavily updated tables smaller fillfactors
The behavior of temporary tables at the end of a transaction block. The three options are:
No special action is taken at the ends of transactions. This is the default behavior.
All rows in the temporary table will be deleted at the end of each transaction block. Essentially, an
automatic TRUNCATE is done at each commit.
The temporary table will be dropped at the end of the current transaction block.
A comments for your table.
This list specifies tables from which the new table automatically inherits all columns.
Use the Columns tab for adding, modifying, and deleting table columns. Please see the
topic Column Editor for the detailed information.
Use the Constraints tab for managing constraints. Please see the
Constraint Editor topic for the detailed information.
The Indexes tab is intended for managing table indexes. Please see the
Index Editor topic for the detailed information.
The Triggers tab is intended for managing table triggers. Please see the
Trigger Editor topic for the detailed information.
The Rules tab is intended for managing table rules. Please see the
Rule Editor topic for the detailed information.
This tab allows you to set SQL statements, which will be executed before (use Begin tab)
and after (use End tab) generation of the table.
The Preview tab displays the SQL statement, which will be executed during the database
generation. This statement is made up according to the changes you have made using previous tabs. Note,
that the text within the editor is read-only.
The Note tab allows you to define a description and an annotation for the edited table.
This properties will not affect the physical PostgreSQL database, but they can be useful for your
These options allow you to set table line and fill color for displaying on the diagram, different
from the default table colors, which are defined within the
Diagram Display Preferences dialog.