You have to specifically create the tables with a non-standard SQL code to get them to use the right database backend to get foreign key support.
The what to the who, now? Dude, if you're using MySQL and you have issues because you can't get past the default storage engine, I can't wait to see what happens when you have to do actual work.
It's not 2000 anymore. 99% of the problems people have historically with MySQL are simply not present in recent production versions. PostgreSQL and MySQL roughly have feature parity nowadays, Stop treating MySQL as if it's some toy. WikiVS has a good, up-to-date comparison: http://www.wikivs.com/wiki/MySQL_vs_PostgreSQL
I also find it amusing that an AC below complains about "how many storage engines"? Whoosh, that's the sound of the point flying over his head.
By the way, I'm not dissing PostgreSQL in any way, I think it's great. But it's about time some meaningless mantras stop being chanted.
I'm sorry? "there's not practical difference between 24fps and 60fps"?
Few people will be able to tell motion above 60fps, sure, but up to that point any human can and will notice the difference. Ever wondered why a movie's motion will look completely different that the motion of your standard news / soap opera / etc? That's the 24-to-30fps difference alone.
Good day to avoid cops. Crawl to work.