Guidelines for extending databases
Modifying sequences is not supported. Editing the sequences.xml file in the entity repository has no effect. Furthermore, IBM® recommends against modifying sequences by using the database tools. Under most circumstances, it is not necessary and has adverse effects.
- Default columns of the default tables
- Primary keys of tables
- Unique keys of tables
- Views
It is recommended that custom or extended columns that are added to the default tables or to
custom tables are set to Nullable=true by default and do not have a default value,
unless it is the primary key column.
Entity relationship diagrams
- Indicate which tables can be extended by adding columns.
- Indicate which tables can have hang-off relationship.
- Relationships between tables (to help you understand the relationship between logical entities such as orders, shipments, and payments).
- Indexes details. Each table is indexed by a primary key. Most tables also have a unique index that is constituted of the columns that make the logical unique key. In addition, some tables have alternative indexes to support queries.
- Views that indicate how several tables interact.
Entity database XML files
The standard tables that are included with the application database are defined in a set of entity XML files, also known as database definition XML files. Each entity XML file might contain several table definitions. To learn more about these tables, see the files in the <runtime_sandbox>/repository/entity directory. Within these entity XML files, an entity represents a table and an attribute represents a column.