Hello, I guess both the hate and the misuse come from misrepresentation. The > "Hibernate in Action" book even goes to great lengths to explain how to do > "long-running conversations that span multiple transactions". > > Does it? I can't even imagine myself manipulating detached, explosive objects.
> That's yet another issue. You can't use stored procedures if you want to > keep migration costs under control. Or, put another way: If you use stored > procedures, you should keep the business logic in the database, and then > any shitty ORM will do and you don't need Hibernate that much anymore. > (...) Hibernate also doesn't even begin to handle bulk queries (...) > Well, I am not a big fan of writing and maintaining stored procedures but sometimes it's the best way to handle bulk operations. It's a bit like comparing DOM and SAX, you use one when you can, the other one when you have to. > Sounds intriguing. > Are there any whitepapers around? > Not sure, it has been a while since I left my previous job and I haven't used it since then. It generated record classes that were somewhat similar to Jooq, along with a representation of their relationships. Some info about fetching graphs can be found here (it's an old version, I am sure it has become much easier): http://www.llblgen.com/documentation/2.6/Using%20the%20generated%20code/Adapter/gencode_prefetchpaths_adapter.htm At loading time, you could basically tell the framework which branches of the object graph should be pre-loaded , this could go to any depth. For example, from an OrderDetail entity it was possible to branch Order, from there you could branch Customer, then Address, Country, anything, the framework would then take care of efficiently filling the graph using either SQL IN clauses or Subqueries. -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
