Comments on: I hate hibernate!

By: Nohibernateever

Nohibernateever — Tue, 22 Nov 2011 03:26:03 +0000

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.

By: Luiz

Luiz — Tue, 08 Nov 2011 18:56:37 +0000

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.

By: EclipseLink a good choice

EclipseLink a good choice — Mon, 03 Oct 2011 04:22:52 +0000

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.

By: EclipseLink a good choice

EclipseLink a good choice — Mon, 03 Oct 2011 04:21:22 +0000

If not Hibernate, then EclipseLink, I have little experience using JPA implementations, but I suspect EclipseLink works better.

By: apfelrigel

apfelrigel — Fri, 26 Aug 2011 22:39:33 +0000

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.

By: Mladen

Mladen — Thu, 16 Jun 2011 11:39:23 +0000

Plain SQL is better than hibernate. Dot.

By: Nathaniel

Nathaniel — Thu, 19 May 2011 14:56:36 +0000

Could not agree more, but….

If not hibernate, then what?

Anybody have experience with using something that works better?

Nat

By: sorin7486

sorin7486 — Thu, 28 Apr 2011 11:57:53 +0000

hibernate is a turd !!!!

By: Another Voice

Another Voice — Mon, 18 Apr 2011 06:53:54 +0000

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

By: Hibernate is great!

Hibernate is great! — Tue, 15 Mar 2011 22:31:32 +0000

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);
}
}

By: Phil

Phil — Thu, 03 Mar 2011 13:12:08 +0000

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.

By: DapperDan

DapperDan — Thu, 20 Jan 2011 23:49:48 +0000

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.

By: Nikolay

Nikolay — Fri, 17 Dec 2010 20:35:11 +0000

“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

By: Alan

Alan — Fri, 22 Oct 2010 16:19:15 +0000

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.

By: Hibernate Sucks

Hibernate Sucks — Sun, 29 Aug 2010 23:34:23 +0000

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!

By: somebody

somebody — Tue, 20 Jul 2010 11:46:48 +0000

agree!

By: LiveFreeOrHibernate

LiveFreeOrHibernate — Sun, 08 Mar 2009 12:22:49 +0000

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!!!

By: PP

PP — Tue, 17 Feb 2009 14:54:04 +0000

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) !!!

By: protokollfuehrer

protokollfuehrer — Thu, 22 Jan 2009 15:56:45 +0000

Yawn…
Nobody forces you to comment on that post.
But now I feel miserable.

By: Eric

Eric — Wed, 21 Jan 2009 18:48:55 +0000

Nobody forces you, to use hypernate.