Re: Naming Convention for Columns

In article <35000C30.6713F614@ene.gov.on.ca>, Allan Burger <burgeral@ene.gov.on.ca> writes >This comment does not solve your argument. > >But some of the low-end CASE tools make the assumption that the column names >must be unique in the database and force you into the standard of tablename >prefixes for columns. > I prefer table name prefixs. When talked to others I if say cd_key then it is obvious which column in which table is wrong "Yeah, it was job 5000 cm_key for the company was wrong." rolls off the tongue better than "Yeah, it was job 5000 company_manager.cm_key for the company was wrong." the dot tens to breaj up the flow... >Allan > >Dave Mullen wrote: > >> Hello all, >> >> We are setting up new database naming conventions, and I'd like to >> hear other people's thoughts on what they consider to be important >> considerations. >> >> In particular, I'd like to know how people feel about prefixing the >> names of columns in a relational data base with a short prefix >> representing the table to which the column belong. ........ > > > -- David Williams Maintainer of the Informix FAQ Primary site (Beta Version) http://www.smooth1.demon.co.uk Official site http://www.iiug.org/techinfo/faq/faq_top.html I see you standin', Standin' on your own, It's such a lonely place for you, For you to be If you need a shoulder, Or if you need a friend, I'll be here standing, Until the bitter end... So don't chastise me Or think I, I mean you harm... All I ever wanted Was for you To know that I care