01 June 2006

Coding Hell #3

Short names are better for performance!

...or at least that is the only kind of reasoning I could find to justify hundreds and hundreds of database tables like the one below...

SQL> desc ttb;
LOC VARCHAR2(15)
DAT VARCHAR2(6)
TIM VARCHAR2(4)
STYP VARCHAR2(2)
SN VARCHAR2(20)
DF1 VARCHAR2(10)
DF2 VARCHAR2(20)
DF3 VARCHAR2(20)
CODES VARCHAR2(20)
WGT NUMBER(6,2)
N0 NUMBER(9)
N1 NUMBER(9)
N2 NUMBER(9)
N3 NUMBER(9)
N4 NUMBER(9)
N5 NUMBER(9)
N6 NUMBER(9)
N7 NUMBER(9)
N8 NUMBER(9)
N9 NUMBER(9)

Needless to say, my predecessors deemed it unnecessary to document any of this in any form. And why should they, the semantic structure of the table is immediately clear, isn't it?

No comments: