Er Abbott wrote:
> "If the column does not accept NULL, it will insert a value based on the column type, in our
> case VARCHAR so we get blank space."
So your "2) NOT NULL? Don't think so..." issue is solved: You and your students don't know the difference between NULL and the empty string.
> mySQL is the only DB I know that applies this absurd rule.
> Sorry if I sound rude, but this rule that mySQL enforces don't make any sense at all.
The MySQL developers have realised that this is not always the wanted behaviour, so from MySQL 5.0.2 onwards you have the option to turning it off.
(See
http://dev.mysql.com/doc/mysql/en/constraint-invalid-data.html).
Onto your 1) "Even using InnoDB tables mySQL didn't took care of referential integrity AT ALL. It was a Bug-Fest:" issues.
Would you care to post the exact statements (including create table and insert) that lead you to the behaviour you described in your original post?
--
felix
Please use
BBCode to format your messages in this forum.