<< An overlap constraint in SQL2K | Home | A BCP GUI >>

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......

Print | posted on Wednesday, March 24, 2004 3:53 PM

Feedback

# Worst naming practices in SQL

left by Enigma at 3/24/2004 1:57 AM
Worst naming practices in SQL

# re: Worst Column Name Ever

left by Enigma at 3/24/2004 4:58 PM
Worst Naming Practices Ever ...

http://sqljunkies.com/WebLog/enigma/archive/2004/03/24/1752.aspx

# re: Worst Column Name Ever

left by robvolk at 3/24/2004 10:42 PM
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. :)

# re: Worst Column Name Ever

left by Enigma at 3/25/2004 1:49 AM
Will have to experiment with that Robvolk ...

# re: Worst Column Name Ever

left by Jeff at 3/25/2004 5:14 AM
How about this:

create table [ ] (i int)
GO
select * from [ ]

# re: Worst Column Name Ever

left by Justin Pitts at 3/25/2004 7:52 AM
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'

# re: Worst Column Name Ever

left by Bob at 3/28/2004 1:45 PM
I like:
create table timestamp (timestamp)
Title  
Name
Email (never displayed)
Url
Comments   
Please add 8 and 1 and type the answer here:
Copyright © byrmol