Slashdot Comment on Reasons to or not to use MySQL:
A nice flame war. I'm just going to sit back, crack a beer and enjoy it. It is almost memorial day weekend, you know. Hopefully it get hot enough in here to roast a hot dog.
Oh goody! I'll help get things going:
- * MySQL users will have to wait until you are done with the fire before they can roast their hot dogs, since MySQL is not a real database and does not support concurrent roasting;
- * I've read the PostgreSQL manual eight times and still can't figure out something as bloody simple as roasting a hot dog, though I did figure out I have to call VACUUM before I can apply ketchup;
- * Serious enterprises who care about their hot dogs use Oracle, since you can roast over 10,000 dogs at once and optionally impart the taste of filet mignon;
- * If you try to roast a footlong hotdog using MySQL it will silently truncate it to regular size, causing your child to cry;
- * Oracle will sue you if you complain about the difficulty of starting your fire or the blackened taste of the dogs;
- * With SQLite your hot dogs are pre-roasted;
- * Last year on Memorial Day, mysqld leapt out of my MacBook Pro and pushed my cousin into the fire, resulting in third degree burns. And also it causes cancer. And terrorism. Blindness. Violent puppy death. BOO! MYSQL IS SCARY DON'T USE MYSQL!!
— Slashdot Comment
| Work | Slashdot Comment |
| Published | 2008-07-04 |