This is a discussion on Re: UNIQUE KEY vs NULLs within the MySQL General forum forums, part of the MySQL category; --> > I have an InnoDB table similar to this: > > CREATE TABLE Target > (IMSI VARCHAR(15) ASCII, > ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| > I have an InnoDB table similar to this: > > CREATE TABLE Target > (IMSI VARCHAR(15) ASCII, > IMEI VARCHAR(15) ASCII, > UNIQUE KEY (IMSI, IMEI)); > > After playing a bit with it, I managed to add duplicate records, if one of > the fields was a NULL: > > +-----------------+-----------------+ > | IMSI | IMEI | > +-----------------+-----------------+ > | NULL | 35195600126418 | > | NULL | 35195600126418 | > +-----------------+-----------------+ > > > Is this a bug, or a feature? :-) A feature. NULL isn't equal to NULL. > If it is a feature, than how can I assure uniqueness for a table in a sense > that won't allow such duplicates? If you don't want to have NULL, use a "primary key" instead of a "unique key". Martijn Tonies Database Workbench - development tool for MySQL, and more! Upscene Productions http://www.upscene.com My thoughts: http://blog.upscene.com/martijn/ Database development questions? Check the forum! http://www.databasedevelopmentforum.com |