On Mon, 9 Apr 2001, Matt Loschert wrote:
Sorry for jumping in ...
> > another NULL Mysql will not complain about it cause Null!=Null whereas
> > it would complain if you had inserted a '1' and tried to insert
> > another '1'.
> >
> > Clear as mud?
> Your explanation makes sense, but it seems a bit counter-intuitive. In my
> mind, if you insert identical values (no matter what they are) into a
> field that is declared to be a unique key, the database should complain
Not really. From a programmers point of view:
define NULL NULL
if(undefined NULL)
# never can be TRUE because it's defined ....
or in other words:
if something is nothing nothing can't be nothing because nothing is 'something' ;-)
Think about it, it's some kind of philosophy :-)
Andreas Karl Wittwer
Phone: +49-7052-92206
FAX: +49-7052-92208
Mobil: +49-172-542 541 4
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
