Is a dbtransaction "open"?

Is there a way to determine whether a transaction is still "open"; i.e., it
hasn't yet been either committed or rolled back? I'm guessing that the
transaction's connection object will be null if it is no longer in use, but
that's just a (hopefull) guess. I've got a situation where the code needs
to determine whether it can use an existing transaction or not, given only
the transaction object itself.

Thanks in advance,
Bill

Hi Bill,

Why would you need it in first place?
--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

"Bill Cohagan" <cohagan (AT) nospam (DOT) nospam> wrote

Is there a way to determine whether a transaction is still "open"; i.e.,
it hasn't yet been either committed or rolled back? I'm guessing that the
transaction's connection object will be null if it is no longer in use,
but that's just a (hopefull) guess. I've got a situation where the code
needs to determine whether it can use an existing transaction or not,
given only the transaction object itself.

Thanks in advance,
Bill

Miha-

Well it's a bit of a long story, but...

I'm implementing a layered architecture, but also want to use lazy load in
my domain objects. In order to keep the domain objects decoupled from the
dataservice I supply each domain object with delegates responsible for
performing the actual fetch when lazy load is invoked. Now it may turn out
that the lazy load gets invoked inside an already existing (and "open" )
transaction in which case I'd like to use that transaction. If that
transaction has already been committed then the lazy load will proceed
without a transaction. The transaction object is captured (via a
WeakReference) in the environment of the delegate that is passed in -- so
I'm allowing for it to have been GC'd as well.

What I'm "lazy loading" are related objects, child sets, etc. Does that
explain it adequately?

Thanks,
Bill

"Miha Markic [MVP C#]" <miha at rthand com> wrote

Hi Bill,

Why would you need it in first place?
--
Miha Markic [MVP C#]
RightHand .NET consulting & development www.rthand.com
Blog: http://cs.rthand.com/blogs/blog_with_righthand/

"Bill Cohagan" <cohagan (AT) nospam (DOT) nospam> wrote in message
news:%23gm8eH2AGHA.360 (AT) TK2MSFTNGP09 (DOT) phx.gbl...
Is there a way to determine whether a transaction is still "open"; i.e.,
it hasn't yet been either committed or rolled back? I'm guessing that the
transaction's connection object will be null if it is no longer in use,
but that's just a (hopefull) guess. I've got a situation where the code
needs to determine whether it can use an existing transaction or not,
given only the transaction object itself.

Thanks in advance,
Bill