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!
October 22nd, 2010 at 18:19
Most of these tools are sacrificing simplicity for the appearance of simplicity. That is, the result
looks simple once it works, but there’s oceans of bytecode rewriting, mysterious foreign key constraint
problems, commits happening in the wrong order, unknown wasteful SQL being executed, and other
stuff happening in the background that you have to control by trial and error. The book is 5 times bigger
than K&R with 10 percent of the intellectual content.
December 17th, 2010 at 22:35
“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”
Oh man, I just couldn’t agree more with this words
January 21st, 2011 at 1:49
Hibernate is a piece of shit. It’s a total waste of time. It doesn’t do anything well. If you want a high performance system, ditch hibernate and use JDBC with stored procs. If you’re coding a POS system with a basic data then use Hibernate. I manage 8 engineers. They end up wasting hours fucking with Hibernate when the solution can be easily accomplished using Stored procs and JDBC.
If you’re tied to Spring: just use the JDBCTemplate. You’ll get everything you get from Hibernate without the bullshit. Hibernate is a total waste of time. There’s no way that it can compete with natively compiled stored procedures and good ole JDBC.
March 3rd, 2011 at 15:12
I couldn’t agree more. I have never come across a single project which has benefitted from having Hibernate in its stack. The problem is the software industry is full of fashion victims and its perpetuated by people like us who need to toe the line in order to get a job. Hibernate and all ORM mapping products are the 80′s shoulder pads of the Java world and it is my guess that in a few years time we will all look back and realise what a bunch of twats we looked.
The other problem is a lot of developers are scared of writing a bit of SQL or a stored proc and would rather spend hours configuring crap annotations and fucking about with badly documented shit like this than actually getting the job done.
March 16th, 2011 at 0:31
Hibernate is an awesome piece of software! I even created my own HibernateBeanFactorySpringInjectedAdapterFramework with it! It works like a charm and I got all my J2EE-certificates.
try
{
HibernateSessionAdapterFactoryImpl h=HibernateSessionFactory.instance().getSession();
SpringAdapterFrameworkImplMapperBeanInterface s=SpringFrameWorkManagerInterfaceHandlerHanlder();
HibernateObjectMarshaller m =getHibernateObjectMarshallerInterfaceWrapperAdapterUtilClassLoader();
m.serializeObject(getObject());
}
catch (HibernateException e)
{
LogFactoryAdapterImplProxyHandler.instance().log(e)
}
catch (SpringException se)
{
if (SpringFrameWorkLogFactoryWrapperHandler.loggerRunning())
{
LogFrameworkWrapperExceptionImplAdapterEnterpriseMapperInjectorBean.log(se);
}
}
April 18th, 2011 at 8:53
Hibernate is a piece of shit. Everybody needs a DAO / data access layer when doing web programming. And hibernate is the so-so features software that screws up 10% of the time but then completely. Waste of energy. Nothing new. Buggy software. Lame documentation.
you get a stacktrace.
you google
you find a bug report
you really ensure this is your bug and not some kind of misconfiguration
you realize this is really your bug
you find out nobody cares
you look at the number of major bugs
you realise this piece of software P.O.S. is also a Piece of shit
April 28th, 2011 at 13:57
hibernate is a turd !!!!
May 19th, 2011 at 16:56
Could not agree more, but….
If not hibernate, then what?
Anybody have experience with using something that works better?
Nat
June 16th, 2011 at 13:39
Plain SQL is better than hibernate. Dot.
August 27th, 2011 at 0:39
Hibernate is a piece of shit. I hate it. After working with it, the last 2 months i am very frustrated. I have to use it, because my comopany uses it but i don’t like it. Hibernate Criteria. Never saw a more useless tool. If you want to do simple things. Nice. But if you have to do a little more complicated things. It fails!!! Documentation is awful. Only simple things are explaned. Real use cases are far from the documented use cases. Hibernate team :” The real worl exists with more than one entity and two relations!!” I was so frustrated, that i have switched to not use Hibernate. Thanks god, i don’t believe in god. My chief said ok,this time. I have read more than four books concerning hibernate. Awful! Same as the documentation. Simple examples, noboby needs it! BlaBlaBla, you can have this job, if you know Hibernate. Sorry, but i think i don’t want this job. I think you don’t know Hibernate.
October 3rd, 2011 at 6:21
If not Hibernate, then EclipseLink, I have little experience using JPA implementations, but I suspect EclipseLink works better.
October 3rd, 2011 at 6:22
BTW, I have not talked to Hibernate development team members, but by the words read in this forum the seem to be bastards, well, everybody that do something that others use believe his/herself Da Vinci, they are assholes, nothing more than that.
November 8th, 2011 at 20:56
I had some problems with Hibernate and JPA too.
I like SQL and transactions. They aren’t problems.
I like OO too, so i’m tring to do something different about:
My Little JAVA ORM here:
http://www.codigorapido.com.br/testeOrm.zip
the source are very simple to understand.
it is just a draft, but is working. I wanna improve it.
If someone like the idea, please send me a e-mail with the subject “I LIKE YOUR ORM” to
luiz-unb@bol.com.br
I’m looking for friends to make something different.
November 22nd, 2011 at 5:26
After struggling for few weeks finally gave up on hibernate. It is simply not suitable for enterprise applications and not for me. really wonder why people try to solve simple problem with complex solution ? Writing sql was so difficult that produced this monster headache causing hibernate ? I will never every touch hibernate. I love SQL and JDBC.