Consultor Eletrônico

Status: Unverified

GOAL:

Dynamics. Entity Naming Conventions

FACT(s) (Environment):

Dynamics 2.0A

FIX:

This Solution describes the conventions you should follow when you name an entity (table or field). Here are some conventions for both types of entities:

1. Choose a name for each entity (table name or field name) that is meaningful, and adequately describes the entity being defined. Avoid general terms such as ·category· and ·type·, which might refer to different kinds of information in different tables in a database, or in other databases that you may need to integrate into your application in the future. Also, generic names such as these run the greatest risk of a conflict with a Progress keyword in a future release of the product. Expand such names into a more specific, more meaningful term (for example, user_category or document_type).

2. Make your entity names singular, (e.g. ·customer·, not ·customers·), if for no other reason than to make query definitions that begin ·FOR EACH customer WHERE·· make some semblance of sense as a sequence of words.

3. Avoid hyphens as separators. The hyphen is not a valid separator in SQL, which you might use at some point to access your database, whether directly or through one of the Progress DataServers. Hyphens also are not valid in Java and other languages from which you might access the database through the Open AppServer. Instead, use an underscore as the separator between the ·words· of an entity name or use mixed case letters. If you use at least one underscore in the name, you guarantee that the name will never clash with any Progress keywords (which never contain underscores).