In fact it seems to be just to opposite. I toggled the default values to
be null and allowed for the null option and "poof" it worked! I don't
really understand this very well. Wish I did.
>
> Some key in the table is null when it shouldnt be, or the type of the join
> keys isnt the same. i h
Some key in the table is null when it shouldnt be, or the type of the join
keys isnt the same. i have had issues when importing data from a dump so
i've had to do a FORIEGN_KEY_CHECKS=0
>
> So I have made a table called 'uid' where on uid is the only field in
> the table. Then I make another table
So I have made a table called 'uid' where on uid is the only field in
the table. Then I make another table called 'users' where there are two
fields, 'uid1' and 'uid2' and both uid values have foreign key
constraints referencing the 'uid' field in the uid table.
No problem, tables are created
