J (9/25/2008)
About using singular names for tables:Good idea.
That name is then suitable for constructs such as
ForEach Officer ...
Looks pretty sorry when it is
ForEach Officers.
In that one case, yes, the singular name looks like it makes more sense. But I don't find:
select Name
from Officer -- Is there only one officer?
to make sense. Update, Insert, Delete and Select look more natural to me when the table name is plural, and I use those a LOT more often that I'd ever use a ForEach contstruct.
That's just an opinion, but it does feel more natural to me that way.
I use singular column names, because each column should contain 1 and only 1 value for each row. Again, totally arbitrary, but it just feels right to me that way. Plural for tables, to indicate the multiplicity of rows, singular for columns to indicate the normalization of the table.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon