clapham_gull
Legacy Fan
- Aug 20, 2003
- 25,877
Managed to send an email requesting a vagina (or something like that) because I didn't check what the spell check did.
Sent from my LG-K520 using Tapatalk
Sent from my LG-K520 using Tapatalk
The boring bit.
On a similiar note when I've built reports in certain languages I have to change the word "count" to something else since it is "reserved" and have a terribly dangerous habit of abbreviating it to "cnt". Anyone who knows SQL knows I'm being lazy and need the qualify the column name as [count] with square brackets.
The reality bit
I have been known to email spreadsheets with a column labelled c*nt on more than one occasion.
Sent from my LG-K520 using Tapatalk
I'm also a purist and my name of choice is c@nt.I am a bit of a purist and never qualify any columns with a reserved word be it in a table ddl or a select I almost always qualify [count] as 'Total'
I'm also a purist and my name of choice is c@nt.
Sent from my BTV-DL09 using Tapatalk
I worked with a really annoying guy who set up databases, table names, columns with spaces in and prefix the column names with an abbreviaion of the data type just wrongness
Columns with spaces is just plain WRONG. The data type prefix is definitely a legacy thing I've seen in a few places.
It's like the guy in my team who writes all his if statements backwards in Java
e.g. if (null != x)
He even tried to convince us it was easier to read. Needless to say, it was everyone else in the team vs him in this debate.
Tell me about it
While 1=1 is the same its C++ and Java devs who are the cuplrits
Also != I dont believe is ANSI compliant should be <> in SQL
and [dtm CallDate] seriously WTF it is indeed legacy nonsense
Also (possibly) stops compilers using tricks like lazy evaluation.Columns with spaces is just plain WRONG. The data type prefix is definitely a legacy thing I've seen in a few places.
It's like the guy in my team who writes all his if statements backwards in Java
e.g. if (null != x)
He even tried to convince us it was easier to read. Needless to say, it was everyone else in the team vs him in this debate.