Enable auto-enlistment by default
---------------------------------
Key: DNET-765
URL: http://tracker.firebirdsql.org/browse/DNET-765
Project: .NET Data provider
Issue Type: Improvement
Components: ADO.NET Provider
Affects Versions: 5.9.1.0
Reporter: Frédéric Delaporte
Assignee: Jiri Cincura
Priority: Minor
The default behavior about auto-enlistment is to have enabled by default. From
Msdn:
> Automatic enlistment is the default (and preferred) way of integrating
> ADO.NET connections with System.Transactions.
https://msdn.microsoft.com/en-us/library/ms254973(v=vs.110).aspx#Anchor_1
This behavior is followed by SqlConnection, SQLiteConnection, SqlCeConnection,
OdbcConnection, OracleConnection (managed & unmanaged), and MySqlConnection.
NpgsqlConnection does not enable it by default in its 3.2 version but has
change that in their code base for the 3.3 version of Npgsql (
https://github.com/npgsql/npgsql/issues/1483 ).
Not having this enabled by default is unexpected for developers used to almost
any other database.
But before enabling it by default, it will likely be required to do DNET-764,
which is about another unexpected behavior which will not play very well with
enabling auto-enlistment by default.
--
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
