I was following this post, http://forum.hibernate.org/viewtopic.php?t=937254, which is from December. Basically, this brings to bear the issue of having to do a session.load() before an update when you may be just changing one column and then you're done. I'm interested to know if a bulk update has been implemented in HB3 or is that still targeted for 3.1? If the road map is current, then it looks like not yet. If so, is there a JIRA issue to track its progress?

My follow-on question is which approach is better to use, especially in light of the new lazy column load feature? I guess I could see lazy columns is pretty cool, so I could just lazily load BIG columns and still load my objects before update like I've been doing for all the obvious lifecycle benefits. But, batch sure is nice when you know just making a column update and don't want to incur the cost of any SELECT.

Just interested in how others are using the new features...Great work and congrats on the new release!

Regards,
Lou

Bulk operations are implemented, but the current implementation has some limitations.

Basically, you cannot use these against any multi-table entities (i.e., <join/>, join or union subclass). Supporting these scenarios is fairly complex. This is what is targeted for 3.1.

But outside those scenarios, the bulk stuff is there and usable since 3.0final...