[FB-Tracker] Created: (DNET-766) Not enabling auto-enlistment should not disable system transactions.

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

[FB-Tracker] Created: (DNET-766) Not enabling auto-enlistment should not disable system transactions.

JIRA tracker@firebirdsql.org
Not enabling auto-enlistment should not disable system transactions.

                 Key: DNET-766
                 URL: http://tracker.firebirdsql.org/browse/DNET-766
             Project: .NET Data provider
          Issue Type: Bug
          Components: ADO.NET Provider
    Affects Versions:
            Reporter: Frédéric Delaporte
            Assignee: Jiri Cincura

It appears that when auto-enlistment is not enabled, explicit enlistment (FbConnection.EnlistTransaction) is disabled too.

The connection string parameter Enlist is normally only about enabling automatic enlistment at connection opening. It is not supposed to disable explicit enlistment.

Found while trying to get NHibernate transaction scope tests working with Firebird: rollback test fails even in a dedicated branch where I have added explicit enlistment. (I was hoping to be able to test that this way, since auto-enlistment breaks the NHibernate tests due to DNET-764). Firebird .Net provider is the only provider tested by NHibernate which behaves in such a way.

Checked in the source, it looks like `Enlist` is not only used for auto-enlistment at connection opening, but also for globally disabling system transactions.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tracker.firebirdsql.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-net-provider mailing list
[hidden email]