I was interested in the comment by someone at RBTI that not allowing
duplicate column names was part of the Codd design. It had been a few
years since I sat at the fire with my Codd book so I did that last evening.
It seems to me if you look at the original 12 or actually 13 rules, rule #2
seems to fit this situation. Rule #2 is usually referred to as the
"Guaranteed access rule" and is usually worded something like this:
"Every value can be accessed by providing table name, column name and key.
All data are uniquely identified and accessible via this
identity."
Now I read that rule that there are 3 things needed to uniquely define a
value or cell to the RDBMS. That is the table name, column name and the
key. So my interpretation of this is that there is nothing in the Codd
rules that says I can't have duplicate column names in differnt tables
because the RDBMS should be defining cell locations by
TableName.ColumnName.Key. And if my TableName name is different, then the
RDBMS should be able to figure out what column I want; the one in
TableName.
So IMHO if the RDBMS is following Rule #2, it should allow us to name our
columns anything we want.
JeffS
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: INTRO rbase-l
================================================
TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED]
In the message body, put just two words: UNSUBSCRIBE rbase-l
