Re: Long column names...Performance issues?

From: toby <toby_at_telegraphics.com.au>
Date: Wed, 19 Nov 2008 15:57:22 -0800 (PST)
Message-ID: <82d67bf3-800f-42ff-b043-8faa6064b0c2_at_w34g2000yqm.googlegroups.com>


On Nov 19, 12:29 pm, chenthorn <car..._at_hotmail.com> wrote:
> 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.

There is no impact on performance whatsoever, so you are free to choose whatever naming convention makes your code most writable, readable and maintainable.

>
> Thanks in advance!
Received on Thu Nov 20 2008 - 00:57:22 CET

Original text of this message