Worst Column Name Ever
While moving some data between servers via BCP from a database that I have never seen before, I noticed that several of the tables failed to load into the target server.
The error message was something along the lines of "Could not cope with *".
What the hell was that!
I was using the native switch so the first thing I did was check the schema of the two…
And what do you know… There is a column (the goddamn Key column) with a "*" in its name…
Just beautiful……
Legacy Comments
|
Enigma
2004-03-24 |
re: Worst Column Name Ever Worst Naming Practices Ever ... http://sqljunkies.com/WebLog/enigma/archive/2004/03/24/1752.aspx |
|
robvolk
2004-03-24 |
re: Worst Column Name Ever I was playing around one day and came up with this one: CREATE TABLE _(_ int not null) That leads to some very interesting SELECT statments. :) |
|
Enigma
2004-03-25 |
re: Worst Column Name Ever Will have to experiment with that Robvolk ... |
|
Jeff
2004-03-25 |
re: Worst Column Name Ever How about this: create table [ ] (i int) GO select * from [ ] |
|
Justin Pitts
2004-03-25 |
re: Worst Column Name Ever But surely not as vexxing as a primary key field typed as CHAR(10) with RIGHT-justified integer content. Not 103 or '103' or '103 ' but ' 103' |
|
Bob
2004-03-28 |
re: Worst Column Name Ever I like: create table timestamp (timestamp) |