Issue Details (XML | Word | Printable)

Key: DNET-765
Type: Sub-task Sub-task
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Jiri Cincura
Reporter: Frédéric Delaporte
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.
.NET Data provider

Enable auto-enlistment by default #breaking

Created: 28/May/17 05:56 PM   Updated: 06/Jun/18 11:45 AM
Component/s: ADO.NET Provider
Affects Version/s:
Fix Version/s:

Issue Links:

 Description  « Hide
The default behavior about auto-enlistment is usually to have it enabled by default. From Msdn:

> Automatic enlistment is the default (and preferred) way of integrating ADO.NET connections with System.Transactions.

This behavior is followed by SqlConnection, SQLiteConnection, SqlCeConnection, OdbcConnection, OracleConnection (managed & unmanaged), and MySqlConnection. NpgsqlConnection does not enable it by default up to its 3.2 version but has changed that in its code base for the 3.3 version of Npgsql ( ).

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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.