> As a result of ambiguity problems with colum names when
> performing a join I discovered that MS SQLServer does not
> return the conventional tablename.columname but only
> columname, which of course creates problems.
>
> I have read quite a lot on the subject and some people
> claim that a colum name should be UNIQUE in a database,
> i.e. rather than having
>
> table1.column
> table2.column
>
>
> the design should be
>
>
> table1.colum1
> table2.colum2
>
>
> This would solve ANY ambiguity as to colum names
> especially in joins.
>
> What is your opinion on that?
>
>
> P.S. Classis DB / SQL literature does not mention this as
> a prerequisite for proper DB design.
>
>
> Adam
>
Typical logical modeling standards that I have seen at
various companies usually state that attribute names are
unique within the model, but not the enterprise. This
doesn't address the typical audit columns one normally sees
in physically implemented tables however. How are those
folks that state that every column must be unique handling
columns like last_update_ts?
Received on Tue Aug 08 2006 - 21:38:35 CDT
