Rick, this is fixed in 3.23.50. I changed InnoDB so that it ignores foreign key checks on keys containing SQL NULL values.
Best regards, Heikki Tuuri Innobase Oy --- Order technical MySQL/InnoDB support at https://order.mysql.com/ See http://www.innodb.com for the online manual and latest news on InnoDB -----Original Message----- From: Rick Flower <[EMAIL PROTECTED]> To: MySQL Mailing List <[EMAIL PROTECTED]> Cc: Heikki Tuuri <[EMAIL PROTECTED]> Date: Wednesday, March 20, 2002 10:56 PM Subject: Inserting records with null foreign keys? >Hi all.. > >I noticed that the current version of InnoDB that is part of MySQL 3.23.47 >does not allow using null foreign keys when doing inserts.. Is this >intentional or a bug? This is allowed by SQL Server as a minimum (a test >is being done by a co-worker currently against Oracle 8i to see how it >behaves). If you don't specify the foreign key, you get a constraint error >on the insert.. We're >just curious if that is supposed to be that way or not.. If that is a >feature, I guess we will have to remove some foreign keys that we've got >defined currently.. Thanks for any input on this! > >-- Rick --------------------------------------------------------------------- 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
