-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 28 May 2004 11:50 am, Martijn Tonies wrote: > This makes perfectly sense. > > So, once again I dare to ask: what's the problem with NULLable > Foreign Keys? It works fine :-) > > (now, who was it that said that FKs should be entered/exist > always?) > > With regards,
Here is the issue... If you go back to what he was doing this insert doesn't work.. INSERT INTO inno3(PK_Col, Child_Col) VALUES (NULL,1) He was trying to use a Primary key as his foreign key to inno2, (in this example of what he was doing). You can't have a null PK as we all know. IT wasn't the foreign key part that was hanging him up.. I think we were on two different tracks and that could have been my fault. Jeff - -- Give me Liberty or give me... well, whatever you think is best for society. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAt28Ald4MRA3gEwYRAk5/AKCId5Bbpgdh6brzxC8H8E70k8tLrgCfUR8N 44Oq/W0lvwdt798hyi5F/6Q= =/8Iu -----END PGP SIGNATURE----- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
