|
|
Posted by Tony Rogerson on 12/28/05 17:47
I agree with 'DATE' and 'DATA' but ID and NAME, it depends on your style.
Its good practice to alias table's on the FROM clause and to specify the
alias when referencing those columns - it helps maintanence by knowing
clearly where columns are referenced from.
create table Logon (
id int not null....
The above declaration for instance, in a SQL statement you would write...
select logon_id = l.id
from Logon l
The table (set) is a container in the same way an object (table) is a
container, the object just contains properties (columns) though rather than
any methods.
My two cents.
Tony.
--
Tony Rogerson
SQL Server MVP
http://sqlserverfaq.com - free video tutorials
"David Portas" <REMOVE_BEFORE_REPLYING_dportas@acm.org> wrote in message
news:1135722026.375744.184650@f14g2000cwb.googlegroups.com...
> Cecil wrote:
>
>> It's blue in SQL Studio but I can't find it in SQL Books on-line. I
>> wanted to use it as a field name but don't like using [].
>>
>> Is it reserved?
>
> It's reserved for the inexperienced who won't bother to come up with a
> more useful and informative name. The rest of us know better because
> we've had too many bad experiences trying to make sense of other
> people's designs with fatuous names like "ID", "NAME", "DATE" or (I kid
> you not) "DATA".
>
> --
> David Portas
> SQL Server MVP
> --
>
Navigation:
[Reply to this message]
|