Re^8: Conditional many to many relationships with Class::DBI

Yes, there are many gotchas in MySQL. There are also many gotchas in Oracle and Postgres. I have two comments on them:

MySQL's gotchas are well-documented. Oracle's aren't. This means that I can learn all the gotchas without losing two days on a production box. I don't know about you, but I never assume that application X will behave just like application Y - I read the manual cover-to-cover at least twice. Every time.
Nearly every single gotcha was the result of a request from a user. And, it's because that behavior was unavailable in the existing systems.

Now, I would love for a setting that would allow me to force the server to error out in many of those gotchas, such as inserting NULL into a NOT NULL column. But, it's like Perl - why must everyone conform to your ideas of correct behavior? Maybe, I like the incorrect behavior. :-)

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

Comment on Re^8: Conditional many to many relationships with Class::DBI