Re: Long column names...Performance issues?

From: Gints Plivna <gints.plivna_at_gmail.com>
Date: Wed, 19 Nov 2008 13:15:56 -0800 (PST)
Message-ID: <1069696d-8855-4ed2-9bce-ae3dfeaaa597_at_j38g2000yqa.googlegroups.com>


On 19 Nov., 19:29, chenthorn <car..._at_hotmail.com> wrote:
> I would like to hear from the community what you all feel are best
> practices regarding naming conventions, and how they affect your
> environment.

I'd say that naming has (almost) nothing to do with performance of code, but it definitely has something to do with performance of coders producing the code. Even with gui tools suggesting variants and helping people not so familiar with schema it is hard to write ThisLongAndWindyVariableNameExactlyDescribingWhatIsItsMainGoalAndExplainingWhyItWasCreatedAsWellAsAddingSomeOtherInfo. On the other hand writing just i, j, k, l, m, n is also very dangerous because it is hard to understand why these were creted, for what used etc etc.
So the problem of course is to find where the golden mean lies. I'm quite sure it doesn't matter where it is exactly for you/your project but there is one thing which matters - stick with your standards. At least in your project. It is hard to work with code having variables: a
ANEWVARIABLE

A_NEW_VARIABLE
a_New_Variable
a_new_variable
v_a_new_variable

ANewVariable
etc
So stick with one standard and use it. My favourite is here http://www.gplivna.eu/papers/naming_conventions.htm yours may be somewhere else :)

Gints Plivna
http://www.gplivna.eu Received on Wed Nov 19 2008 - 22:15:56 CET

Original text of this message