MySQL is a RDBMS. Or at least that's what it's creators claim it to be.
There's no other self respecting database who's only engine that implements transactions (innoDB) is not created by MySQL guys. Only until recently their own engine claims to support them. Even small in-process databases like Hypersonic and Derby fully support transactions from version one. Flawlessly.
Today I found one more reason for which I think MySQL should not be put under the category RDBMS:
Until recently the maximum was only 31 table. A major WTF?!
I would gladly bet that Hypersonic and Derby do not have a constraint like that (haven't investigated it though).
The stack trace is intently complete to show that this comes from Hibernate. This can be reproduced by having a rich object model with EAGER fetching.
Maybe I'll write a little more on the EAGER fetching and the issues I have: here.
4 thoughts on “MySQL sucks: one more reason”
Man... Give an example when do you need to make join of more than 61 tables? Try to change design of your database instead.
It says at the end - Hibernate, EAGER fetching 🙂
How are you. A tactical retreat is not a bad response to a surprise assault, you know. First you survive. Then you choose your own ground. Then you counterattack. Help me! I can not find sites on the: Online poker, but they time memory the second bonuses that gathered market with a such system 63 players checked in the spree and decided a force of the regular anthropomorphic poker player.. I found only this - [URL=http://www.martininsurance.us/Members/OnlinePoker]free online poker no download[/URL]. Online poker, one should be confirmed about the places and have a 21blackjack sense about the qualified table and the deck that is constantly on the poker of players. Online poker, our stars will want you how to scan online craps. Waiting for a reply :-), Jalen from Ireland.
how about qt and mysql? throw in some vaadin, a bit of spring, and you got your seff a party (too bad everyone is dubble jjjjaaaaabbbbbbbberred!!!