>>Something I think about things that I should not be thinking about (is it called being neurotic <g>?)
>>
>>I am designing a new database and of course new tables. A few sample databases I see (in VFP and in SQL Server) use convention of naming tables as plural (Categories, Companies, Products, etc.) It has always bothered me why they do that.
>>
>>I think that naming tables with singular names makes more sense. Like Category, Company, Product, etc. I see a few benefits of using singular names:
>>1. Fewer letters to type in code.
>>2. When you type COMPANY.ADDRESS it means "one company address", whereas if you type COMPANIES.ADDRESS it is confusing. Am I making sense? <g>.
>>3. Ok, not a few, just two <g>.
>>
>>But there must be reasons why all the database gurus use plural names. What are they?
>
>Dimitry
>
>not an answer to your question but -
>
>I would have thought that provided you have a naming scheme of some sort and are consistent you should call your tables whatever you like.
>
>Nick Mason
I agree, consistency is the key! I just wanted to be sure that I am not missing something adopting a "non-conventional" convention <g>.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
