Long column names...Performance issues?

#31

On 19 Nov., 21:26, patrick... (AT) yahoo (DOT) com wrote:

Quote:

I remember one coder used to name his variables after random star trek
characters and episodes.

He was somehow limited in his imagination. I think the very first
technique offered here http://www.web-hits.org/txt/codingunmaintainable.html
(New Uses For Names For Baby) is much better.

Gints Plivna
http://www.gplivna.eu

#32

On 19 Nov., 21:26, patrick... (AT) yahoo (DOT) com wrote:

Quote:

I remember one coder used to name his variables after random star trek
characters and episodes.

He was somehow limited in his imagination. I think the very first
technique offered here http://www.web-hits.org/txt/codingunmaintainable.html
(New Uses For Names For Baby) is much better.

Gints Plivna
http://www.gplivna.eu

#33

On 19 Nov., 21:26, patrick... (AT) yahoo (DOT) com wrote:

Quote:

I remember one coder used to name his variables after random star trek
characters and episodes.

He was somehow limited in his imagination. I think the very first
technique offered here http://www.web-hits.org/txt/codingunmaintainable.html
(New Uses For Names For Baby) is much better.

Gints Plivna
http://www.gplivna.eu

#34

On 19 Nov., 21:26, patrick... (AT) yahoo (DOT) com wrote:

Quote:

I remember one coder used to name his variables after random star trek
characters and episodes.

He was somehow limited in his imagination. I think the very first
technique offered here http://www.web-hits.org/txt/codingunmaintainable.html
(New Uses For Names For Baby) is much better.

Gints Plivna
http://www.gplivna.eu

#35

On 19 Nov., 21:26, patrick... (AT) yahoo (DOT) com wrote:

Quote:

I remember one coder used to name his variables after random star trek
characters and episodes.

He was somehow limited in his imagination. I think the very first
technique offered here http://www.web-hits.org/txt/codingunmaintainable.html
(New Uses For Names For Baby) is much better.

Gints Plivna
http://www.gplivna.eu

#36

On 19 Nov., 21:26, patrick... (AT) yahoo (DOT) com wrote:

Quote:

I remember one coder used to name his variables after random star trek
characters and episodes.

He was somehow limited in his imagination. I think the very first
technique offered here http://www.web-hits.org/txt/codingunmaintainable.html
(New Uses For Names For Baby) is much better.

Gints Plivna
http://www.gplivna.eu

#37

On 19 Nov., 21:26, patrick... (AT) yahoo (DOT) com wrote:

Quote:

I remember one coder used to name his variables after random star trek
characters and episodes.

He was somehow limited in his imagination. I think the very first
technique offered here http://www.web-hits.org/txt/codingunmaintainable.html
(New Uses For Names For Baby) is much better.

Gints Plivna
http://www.gplivna.eu

#38

On Nov 19, 12:29*pm, chenthorn <car... (AT) hotmail (DOT) com> wrote:

Quote:

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.

Quote:

Thanks in advance!

#39

On Nov 19, 12:29*pm, chenthorn <car... (AT) hotmail (DOT) com> wrote:

Quote:

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.

Quote:

Thanks in advance!

#40

On Nov 19, 12:29*pm, chenthorn <car... (AT) hotmail (DOT) com> wrote:

Quote:

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.

Quote:

Thanks in advance!