This gets modded Insightful?

What is the meaning? That teenage boys are smart and teenage girls stupid? Or that boys are selfish and don't think people should be payed for what they do, (unless they suddenly form a boy band, in which case they probably would want to get payed), and that girls have more empathy and are ok with paying artists/the labels or otherwise buy indie?

I can't think of a single reading of that stupid sentence that would make it 'Insightful'.
Is it because the slashdot crowd is mostly computer nerds? Does that mean computer programmers? As in, say, Grace Hopper?

All of this is handled properly since v5.0
However, for backwards compatibility, the default mode is that of older MySQL versions, and hence you get default values for invalid data when constraints aren't met.

However, these don't go silently. It's true that an error isn't thrown, but warnings are generated every time a column is truncated or set to it's default data type.

If you want an error while inserting null into a not null column, or while inserting an out of range value, setting sql_mode into something like 'STRICT_TRANS_TABLES' or 'TRADITIONAL' will make MySQL work the way you expect.

It's true that combining MyISAM and Innodb tables in transactional statements will screw up your data, but that's only because you shouldn't be using MyISAM tables in transactions in the first place! If you want transactions, use InnoDB, or BDB, if you need something else. InnoDB is good for 99.9% of the cases in which transactions are needed for MySQL. Complaining that your referential constraints and transactions aren't respected while MyISAM tables are involved is like, I don't know, trying to write data to a closed socket and then complaining that it blows up in your face :)

All of this is properly documented in the manual. As any complex piece of engineering, one shouldn't try to do anything big with MySQL without reading the corresponding manual sections first, or unexpected behavior will arise, and frustration/anger is sure to follow :)

I wouldn't blame postgresql for any bad performance I may get out of it, I would blame my lack of knowledge, since I know next to nothing about it.

Finally, I believe this 'war' thing is just among people who don't really contribute much to either project. The Percona conference is coming by the end of april, and some PostgreSQL folks are giving talks there too, so I'm confident that the hacker community is well above any occasional flamewar :)

In MySQL, "coryking", "CorYKING" and "CORYKing" may or may not be all the same, depending if the datatype is binary (they wouldn't be the same) or non-binary (the could be the same or not, depending on the charset and collation). You probably had a case insensitive collation on MySQL. I don't know much about Postgresql so I don't know what could have changed on your schema there, but the bottom line is that MySQL *is not case-insensitive*, individual string data types can be case sensitive or insensitive, depending on your application needs. It really pays to RTFM :)