Database Reference
In-Depth Information
Note
The degree to which you use prefixes within a table is a matter of style. When a
table contains generic field names, some database designers will choose to prefix
the generic names only, while others elect to prefix
all
of the field names within
the table. Regardless of the prefix method you choose to use, it is very important
that you use it consistently throughout the database structure.
I personally prefer to prefix the generic field names only, and I'll follow this pref-
erence throughout the remainder of the topic.
•
Use the minimum number of words necessary to convey the meaning of the charac-
teristic the field represents.
You want to avoid lengthy field names, but at the same
time, you also want to avoid using a single word as a field name if that word is in-
appropriate. For example, if you're trying to record the date a particular employee
joined the organization, “Hired” is too short (and slightly vague) and “Date That
the Employee Was Hired” is too long! “Date Hired,” however, is a more appropri-
ate name and accurately represents the characteristic the field represents.
•
Do not use acronyms, and use abbreviations judiciously.
Acronyms can be hard to
decipher and often lead to misunderstanding. Imagine a field named “CAD_SW.”
How would you determine what the field represents? On the other hand, you can
use abbreviations so long as you use them sparingly and handle them with care.
Only use an abbreviation if it supplements or enhances the field name in a positive
manner. An abbreviation shouldn't make a field name ambiguous or diminish its
meaning.
•
Do not use words that could confuse the meaning of the field name.
A field name
that contains redundant words or synonyms can make the name's meaning unclear
and subject to misinterpretation. For instance, consider the name “Digital Identific-
ation Code Number.” “Digital” and “number” are redundant, so you can eliminate
either one without diminishing the field name's meaning. Let's assume that you
decide to eliminate “digital.” You can split the remaining name into two smaller
names: “Identification Code” and “Identification Number.” These names are often
synonymous, and you can easily use either as the final field name. In this situation,
just use the name that is most meaningful within the organization.
•
Do not use names that implicitly or explicitly identify more than one characteristic.
These types of names are easy to spot because they typically use the word
and
or
or.
Field names that contain a slash (\) or an ampersand (&) are dead giveaways as
well. When you encounter a field with a name such as “Area or Location” or
