Integration with System.Transactions

[GoogleCodeExporter]

Currently we don't integrate with System.Transactions. But we must: if 
underlying connection we use is enlisted in distributed transaction, we must 
get pre-commit & rollback notifications to flush our Session-level caches.

In particular, this implies we must implement VolatileResourceManager at 
least.

Useful links:
- http://www.developer.com/net/net/article.php/3565196
- http://msdn.microsoft.com/en-us/magazine/cc163688.aspx
- http://msdn.microsoft.com/en-us/library/ms229975.aspx

Original issue reported on code.google.com by alex.yakunin on 2 Aug 2009 at 2:46

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

We are writing in some custom cases in an external database : this could 
practical instead of doing our custom synchronization between the two 
transactions. But this is useful only for drivers supporting it: Oracle? I 
don't know for ODBC drivers in general.

Original comment by julien.b...@gmail.com on 18 Oct 2010 at 7:39

[GoogleCodeExporter]

As far as I can judge, all the DBMS supported by DataObjects.Net (MSSQL, Oracle 
and PostgreSQL) already support distributed transactions managed by 
System.Transactions. So all we need here is to provide integration with their 
API + ensure our write cache is flushed before commit of distributed 
transaction.

Original comment by alex.yakunin on 18 Oct 2010 at 10:02

[GoogleCodeExporter]

Probably a dumb question : With this we could use a distributed transaction for 
a transaction without DO.Net and another transaction with DO.Net, right?

Original comment by julien.b...@gmail.com on 18 Oct 2010 at 10:17

[GoogleCodeExporter]

Yes, certainly.

Original comment by alex.yakunin on 18 Oct 2010 at 10:21