Hi,

I don't want to be mean to Hibernate users, but I really cannot understand how anyone can map object with relation. It doesn't make sense. It should be objects HAVE relations, and the relations can be described and maintained by SQL. Therefore, it seems to me Hibernate is pointless.

So all the fuss is just for persistency, and let's see what is persistency. First you get your persistent model for your business logic, and then you translate it to SQL to implement it. What is the point to add all those XML mapping stuff? Map for what?


Freakie

I find hibernate useful, because in implementing projects, the most annoying work for developers is persistence. Secondly the process is always the same.

Hibernate is my first choice, as the persistence mechanism can be used with jboss as it is. Now with ejb3, the difference is very little if any.

No problem to explain.

In a complex system you will have many objects, which are related to each other. Unfortunately users have this weird idea that they shouldn't have to key in data everytime there's a power cut so they insist on persisting this data.

Now there are many methods for persisting data, my personal favourite is paying small children to inscribe the data on the side of matchsticks until they go blind. Failing that I use hibernate because there is nothing more boring than spending time writing SQL just to persist objects.

With time and effort you can do almost anything with SQL, but I don't want to spend time and effort doing dull routine nonsense which leaves me tied to a db. Or having to maintain a small mountain of SQL and constantly thinking about the associated code and security issues.

Hi,
Persistence on matches is really a good idea... I'd tell my boss to buy 1 or 2 childrens.


So, you think it's boring to type SQL queries, but to perform fine tasks with hibernate, you've got to type HQL queries.

HQL is not so easy to use (I've got to learn), in some aspect, it's hard to get the result. It is not as flexible as SQL.
Secondly, if you build a good architecture (DAO, value Object, Services Object, ...) using the good old JDBC, it's not so hard to maintain.....

Hibernate, sometimes, is really to heavy.

HQL, yeah you can use it. But strangely enough I don't seem to actually use it very much. I tend to use criteria and querying by example. But even if you did write HQL queries you still don't have the amazingly dull task of retrieving and storing objects in a db.

Yes hibernate is sometimes too heavy for trivial apps, but many of us don't write trivial apps. We write apps which take time to develop, have many complicated issues and cause us much pain. Hibernate is the ibuprofen of the movingDataBetweenDBsAndObjectsAndThingsWorld.