|
|
Posted by Erland Sommarskog on 02/24/07 09:50
--CELKO-- (jcelko212@earthlink.net) writes:
>>> For example, imagine that my initial table has the columns ID, Name,
Salary with the constraint that Salary is not NULL. <<
>
> Your data element names are all wrong. There is no such magical
> creature as a Universal ID; this is OO or file system record numbers.
> Name of what? Employee, maybe? Salary_type? Salary_amt? In fact, we
> have no ideas what the name of this table is!!
Joe, in your endeavour to spit on as many SQL users as posssible, can't
you just be a little bit discriminant? Emin's question was apparently of
a generic nature, and his table was just an exmaple. For a table that
is just to be used in an example, and nothing else I think "id" is a
perfect name. There is no reason to call it CheeseID, AppleID, or
WhateverID; that would only distract attention from what the example
is intended to discuss.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Navigation:
[Reply to this message]
|