I hate hibernate!
May 7th, 2008 at 15:56 by protokollfuehrerEvery day another hibernate fuckup! And it is not (only) my poor understanding of it! It’s the unsufficient documentation. It’s the bad written book. It’s the arrogance of the hibernate team members in their forum. It’s the way they handle bugs. It’s their inconsistence with these two totally separated query-languages. It’s their proxy-fuckup. And i’m not alone with that perception…
August 28th, 2008 at 19:32
I totally agree with you
September 19th, 2008 at 20:16
In their documentation, even the most basic concepts are poorly, confusingly, sometimes contradictorily documented.
And it is very irritating, the arrogance with which they treat people asking questions in their forums.
January 21st, 2009 at 20:48
Nobody forces you, to use hypernate.
January 22nd, 2009 at 17:56
Yawn…
Nobody forces you to comment on that post.
But now I feel miserable.
February 17th, 2009 at 16:54
Actually, I don’t see any point on such frameworks. The great majority of their users develop inhouse and expert systems that are more likely to NEVER change the underlying database!
What do people expect to abstract with that crap? Not mentioning the effort spent on the seas of XML configuration that could be as well employed on decent code to do the same abstraction (considering that it is really needed) !!!
March 8th, 2009 at 14:22
Wow. Agree. Agree. Agree. Agree.
IMO Hibernate does do quite a few cool things. But the cost in using it is much too high – it’s like u need a PHD in Hibernate to use it properly. There are many things I hate about it, but you pretty much nailed the big ones.
The documentation IS awful.
The crazy configurations you have to come up with for real simple SQL operations.
HQL! The so-called ‘extension’ to SQL. It’s not an extension… it’s a replacement! Was ANSI SQL not good enough?
Oh yes and the Hibernate nazis on the Hibernrate forum! ‘You’re free NOT to use Hibernate’. I have news for you, jerky, I am NOT free to not use Hibernate cuz I am now in charge of an app that was built with it!!!
July 20th, 2010 at 13:46
agree!
August 30th, 2010 at 1:34
I just got through trashing hibernate after spending far too many hours and days working out what should be simple stuff. I was led to believe that using annotations would make it easier to use with less headaches. WRONG!!! Example…
Trying to map relational tables from a single entity. User with many UserEmails. After lots of headaches, I FINALLY got it to work with little help from the documentation and especially the condescending forum rats. Then, all I wanted to do was add another single entity InvoiceType which in no way had anything to do with the two entities above…NONE! As soon as I add this new annotated entity class, I start getting: “org.hibernate.DuplicateMappingException: Duplicate collection role mapping com.lostproperty.model.User.userEmails”. Keep in mind I’m using annotations and NO cfg file. I remove the InvoiceType from the session creator and the message is gone and works fine.
That it totally and completely messed up! I completed my second day now banging my head against the computer monitor before deciding to chunk hibernate into the trash. I would set it on fire and stomp on it’s ashes if that was physically possible. It’s too bad that a growing number of shops are using it…or trying to at least.
Nice to see others having the same issues. We need to start a support group!