Shane,

> I think that there should be nested transactions. Having nested
> transactions allows users to write classes that can use transactions,
> without other developers who might interface to the class breaking the
> class by having a transaction of their own.
>
> Just my thoughts.

I think this feature is discussable ... I, for one, have never, ever had
the need for nested transactions.

My classes never started the transactions - they don't need it.

Even if I have special classes, ORBs or POMs in anyway, it's
the application, not the middle-layer/business objects/etc that
use the transactions (in my apps). And hey, I've also never needed
to save _part_ of my stuff - because when that happens - there's
still something terrible wrong :)


With regards,

Martijn Tonies
InterBase Workbench - the developer tool for InterBase & Firebird
Firebird Workbench - the developer tool for Firebird
Upscene Productions
http://www.upscene.com

"This is an object-oriented system.
If we change anything, the users object."