Kbase P25832: Dynamics. Good Database Entity Naming Principles
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/05/2003 |
|
Status: Unverified
GOAL:
Dynamics. Good Database Entity Naming Principles
FACT(s) (Environment):
Dynamics 2.0A
FIX:
1. Make entity (table/field) names meaningful, specific, and singular in number.
2. Avoid hyphens in names Consistently use underscores or mixed case to delimit text in names Give the same name to fields in different tables that can be joined on; don·t give the same name to similar fields that aren·t in fact join fields.
3. Make table names and Progress dump names unique across all your application databases wherever possible; Dynamics cannot provide some of its standard features such as record-based comments if dumpnames are not unique.
4. Keep dumpnames to five to eight characters if possible; this is the Dynamics five letter acronym (FLA).
5. Follow the conventions that Dynamics uses in its Repository: a three-character prefix plus underscore, identifying the type of data in the table and its database.
6. Keep entity names to a reasonable length (32 characters maximum).
7. Use domains to organize database fields into categories, each with a specific format. etc.