A table must have a unique Table Name such as CUSTOMER or APPLICATION_USER. A table name is spelled all-uppercase and may contain underscores but not spaces. The table name is used when generating the physical RDBMS table.
|
A table must have a unique Abbreviation such as CST or APP_U. The Abbreviation is of no great consequence for your model and rules.
|
A table must have a unique Object Name such as "Customer" or "Application user". An Object Name may contain lowercase characters and spaces and is typically in the singular. The Object Name is of no great consequence for your model and rules.
|
A table must have a unique Object Name Plural such as "Customers" or "Application users". An Object Name Plural may contain lowercase characters and spaces and is typically the plural of Object Name.
The Object Name Plural is used in the default application in the View, Objects dialog. In its variant form with underscores ("Application_user" for "Application user") it is used in XML that USoft produces and is able to import. This includes XML that is returned to REST service calls that specify XML as a format.
|
For a table T2, you can set the Supertype table attribute to the name of a different table, say T1 that is defined in the same instance of USoft Definer. This establishes a structure in which T2 is a subtype of T1 (and T1 the supertype of T2). Further tables could, in turn, have T2 as a supertype. Also, multiple tables can have Supertype = T1, in which case they are all subtypes of T1.
|
If Supertype has a value, you can set Create Separate Table = Yes (the default) to cause USoft to create a separate database table for the table being defined. The table's primary key must be identical to the primary key of the supertype (see Supertype).
You can set Create Separate Table = No to cause USoft to implement supertype and subtype columns in the same physical database table.
|
If Supertype has a value, you can set Delete Super on Delete = Yes (the default) to cause USoft to delete a supertype record when the corresponding subtype record is deleted.
You can set Delete Super on Delete = No to cause USoft to keep the supertype record when the corresponding subtype record is deleted. This option applies only if Create Separate Table = Yes.
|
If the table being defined is part of an application that you expose to other applications as a module, you can set Interface = Yes to signify that the table must be made accessible to the consumer application. You can set Interface = No (the default) to signify that the table must be hidden from, not exposed to consumers.
|
You can find this table attribute on the Table Details tab in the Database Tables window. Its value is used to calculate the initially allocated table space in the RDBMS. Good estimates of required table space decrease table fragmentation and increase performance.
|
You can find this table attribute on the Table Details tab in the Database Tables window. Its value is used to calculate additional required table space in the RDBMS when the table grows after it was initially created. Good estimates of required table space decrease table fragmentation and increase performance.
|
You can find this table attribute on the Table Details tab in the Database Tables window. It allows you to read a table into memory the first time it is used during a user session. Do this only if the table is rarely updated, by setting Static = Client (the default is No). This may increase performance during subsequent use.
You can set this attribute to Rdbms to prevent a parent table that is rarely changed, but constantly referenced by data manipulation on a child table, from being locked.
|
|
