[hibernate-dev] [OGM] Demarcating units of work

Hardy Ferentschik hardy at hibernate.org
Wed May 6 16:00:15 EDT 2015


On Wed, May 06, 2015 at 10:13:38AM +0100, Sanne Grinovero wrote:
> I do agree with you that it's kind of weird that people write code
> without making transactional requirements explicit in the code, but it
> seems that the trend is to abstract from that and use the
> "Transaction" term as a "Unit of work".

What are you referring to? Where do you see this trend.

> For example I find it strange that - in Java - one has to configure
> the isolation levels of transactions to the safest (least efficient)
> option possible among the types his *various* use cases require. It's
> pretty obvious that it would be more efficient to choose those levels
> as "profiles" based on use case, possibly bean or even method level.
> I guess that's were complex applications split up in multiple deployments..

I am not sure I am quite following you on this.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 496 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/hibernate-dev/attachments/20150506/6a5e0358/attachment.bin 

More information about the hibernate-dev mailing list