Dependent objects are automatically hidden in the database tab since they will be available as sub-tabs or sub-forms of the parent object. An object is dependent if it is the child of a dependent relationship. The hidden option allows objects to be explicitly specified as hidden or visible in the database tab.
The primary key is the set of columns that contain values that uniquely identify each row in the table. Specifying a primary key for your table has many benefits:
A good primary key is composed of a set of columns that are immutable (they don’t ever change). By only including immutable columns you can avoid deferencing references from other tables or expensive cascade updates. A column must be required in order to be used in the primary key.
With Database Explorer you can specify soft primary keys for your views. A soft primary key is the set of columns that contain values that uniquely identify each row in the view. While soft keys are not enforced in the database, they allow Database Explorer to improve your experience in many ways:
A good primary key is composed of a set of columns that are immutable (they don’t ever change). By only including immutable columns you can avoid deferencing references from other tables or expensive cascade updates.
Keep in mind that the uniqueness of soft keys are not enforced in the database. Specifying a set of columns that does not actually uniquely identify each row will lead to unpredictible results.
The table does not have a primary key constraint so the best available unique index will serve as the primary key. The best available unique index is the named “”. an unnamed .
The natural key is the set of columns that contain values that uniquely identify each row TO THE USER in the table. If a natural key is not specified, Database Explorer will use the primary key. The natural key is used to identify rows to the user in many contexts including lookups and navigation paths. When a natural key is specified for a table, the database will enforce uniqueness which improves data quality. When a natural key is specified for a view, uniqueness is not enforced in the database.
The table does not have a non-primary unique index to define the natural key. The primary key will be used as the natural key.
By default Database Explorer will sort rows by the natural key. Specify an order by when you would like to sort row differently from the natural key. Uniqueness for an order by specification is neither required or enforced.
The table does not have an order by specification. The natural key will be used.
The results of your query will be saved as new table with the name you provide.
The query will be saved using the name you provide. It will show the current data each time you open it.