http://www.sommarskog.se/dynamic_sql.html

and run sometimes these 2 queries on your SQL Server that used for Hibernate

select SUM(SC.pagesused)*8192/1024 as [Procedure buffer (execution plans) size Kbytes] from [master].dbo.syscacheobjects SC

select
SC.cacheobjtype
,SC.objtype
,SC.sqlbytes
,SC.pagesused
,SC.usecounts
,SC.[sql]
from [master].dbo.syscacheobjects SC
–where usecounts = 1
ORDER BY SC.pagesused DESC

Pay attention to the size of RAM occupated by queries with usecounts = 1 - it is mostly wasted for nothing.

I suggest you read up on Unit of Work pattern as Hibernate carries it out in a great manner.

Nope, I certainly did not mean to imply that. I peeked at the hibernate architecture some years ago and rejected it. Currently we are using EclipseLink for some aspects of our project. It has some nice autogenerate features which so far works great on derby, SQLServer and PostgreSQL. The real ‘meat’ of our relational model, however, is ROLAP and for that we’re not using JPA.

Pathetic. They even need the Spring team’s help getting their “framework” to a tolerable level of usability.

Have fun figuring out all of those retarded caveats while those idiots work on the next version of Crapbernate, and you have to start all over again. The rest of us will actually be completing our software projects in the mean time. ROFFLE

And “jimmy” if you mean to imply that Hibernate is not crap piled upon more crap internally (take a look at the awesome source code), you are either delusional or you have special needs.

Hibernate is for lazy developers who think they can avoid work by using some crap ORM tool. They fail to realize just how much time it costs them getting the ORM crap to do what it’s supposed to do in the first place. And by the time you’ve learned it and become good with it–there’s a new version out and you’re a Hibernate tard again. If they had just focused on simplicity and sat down to do the work in the first place, they’d have been done before they reach the point where they discover new “issues” in Hibernate’s caching, logging, performance, etc. AND even the latest college graduate would be able to understand how it works.

Hibernate = job security perhaps? That’s about it.

iBatis is a dumb toy.
Consider the fact that returning autogenerated keys requires ** different ** xml depending on the database (derby VS. sqlserver), what’s the whole point of “shielding” yourself from DB vagaries if each DB has its own XML syntax?

Now get the spring wannabes in there, and you have a crap wrapper around a crap wrapper around pure JDBC. That’s at least 15 layers of crap!

Instead, I found it was a pleasure to use iBatis as I had full controls over SQLs and my code was much more concise.

HibernateTemplate ht = getHibernateTemplate();
ht.save( b );
ht.flush();

and this resulted in all those mysterious errors that the article talks about.

I would definitely not prefer Hibernate over simple C++ or over the great ORM capabilities of Ruby on Rails. At least we have complete control of the exceptions and errors in the case of C++ or RoR. That way hibernate sucks, not even a good post in net for this problem from the Hibernate team and above all the team tries to defend themselves for their follies.