Re: 3NF question
Date: 12 Jan 2005 15:55:48 -0800
Message-ID: <1105574148.725975.63860_at_c13g2000cwb.googlegroups.com>
>> I'm not sure what the answer is to the whole naming question, but
The context it appears in is the whole schema, not a table. You do
have a data dictionary, don't you? And it applies to the whole data
model, right? You are confusing Cobol file declarations with RDBMS
table declarations.
If an "employee_salary" is logical different from other salaries,then
it needs that name. It is not, then you might have "salary_amt" ,
"salary_grade", etc. that give the attributes of that entity in your
model.
The rule for identifiers is:
can't the column name "id" be interpreted in the context of the name of
the table in which it appears? <<
1) Use the industry standard if you have one
2) Look for a natural key if you have one
3) carefully define your own key (check digits, vlaidation rules, etc.)
only if you must.