Long column names...Performance issues?

My group is working to create a new set of Db standards as we embark upon redesigning our new web app backend db. The other architect wants every table/column/variable name to be unabbreviated and as descriptive as possible. This of course leads to long and ungainly names. while this is all well and fine in theory, when writing a lot of code, long column names are no fun and often lead to bugs due to spelling errors (Not that I would know anything about that )

I would like to hear from the community what you all feel are best practices regarding naming conventions, and how they affect your environment.

Thanks in advance! Received on Wed Nov 19 2008 - 11:29:27 CST