Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable auto-enlistment by default [DNET765] #707

Closed
firebird-automations opened this issue May 28, 2017 · 7 comments
Closed

Enable auto-enlistment by default [DNET765] #707

firebird-automations opened this issue May 28, 2017 · 7 comments

Comments

@firebird-automations
Copy link

Submitted by: Frédéric Delaporte (fredericdelaporte)

Depends on DNET764
Jira_subtask_inward DNET791

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 http://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 up to its 3.2 version but has changed that in its code base for the 3.3 version of Npgsql ( npgsql/npgsql#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 DNET764, which is about another unexpected behavior which will not play very well with enabling auto-enlistment by default.

Commits: 3ce7a82

@firebird-automations
Copy link
Author

Modified by: Frédéric Delaporte (fredericdelaporte)

description: The default behavior about auto-enlistment is to have enabled by default. From Msdn:

> Automatic enlistment is the default (and preferred) way of integrating http://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 ( npgsql/npgsql#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 DNET764, which is about another unexpected behavior which will not play very well with enabling auto-enlistment by default.

=>

The default behavior about auto-enlistment is to have enabled by default. From Msdn:

> Automatic enlistment is the default (and preferred) way of integrating http://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 up to its 3.2 version but has changed that in its code base for the 3.3 version of Npgsql ( npgsql/npgsql#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 DNET764, which is about another unexpected behavior which will not play very well with enabling auto-enlistment by default.

@firebird-automations
Copy link
Author

Modified by: Frédéric Delaporte (fredericdelaporte)

description: The default behavior about auto-enlistment is to have enabled by default. From Msdn:

> Automatic enlistment is the default (and preferred) way of integrating http://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 up to its 3.2 version but has changed that in its code base for the 3.3 version of Npgsql ( npgsql/npgsql#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 DNET764, which is about another unexpected behavior which will not play very well with enabling auto-enlistment by default.

=>

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 http://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 up to its 3.2 version but has changed that in its code base for the 3.3 version of Npgsql ( npgsql/npgsql#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 DNET764, which is about another unexpected behavior which will not play very well with enabling auto-enlistment by default.

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Fix Version: vNextBig [ 10850 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

Link: This issue depends on DNET764 [ DNET764 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

issuetype: Improvement [ 4 ] => Sub-task [ 5 ]

Parent: DNET791 [ 21933 ]

@firebird-automations
Copy link
Author

Modified by: @cincuranet

summary: Enable auto-enlistment by default => Enable auto-enlistment by default #⁠breaking

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants