At 11:26 AM 12/14/2002 -0600, Shane Vincent wrote:

>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.

I'm not convinced that nested transactions are what is required
for this type of programming. The model we used originally included
multiple, independent, named transactions per connection. The
capability still exists, it's just not surfaced in SQL


Regards,

Ann
www.ibphoenix.com
We have answers.