We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Submitted by: @cincuranet
Relate to CORE1851
Test case: FbConnectionStringBuilder builder = new FbConnectionStringBuilder(); builder.Database = "test"; builder.ServerType = FbServerType.Embedded; builder.UserID = "SYSDBA"; builder.Password = "masterkey"; <//builder.Pooling> = false; FbConnection.CreateDatabase(builder.ToString(), true); new FbConnection(builder.ToString()).Open();
and the application freezes at the end. Uncommenting the line solves the problem. The 2.0.3 version is OK.
The text was updated successfully, but these errors were encountered:
Component: http://ADO.NET Provider [ 10041 ]
Sorry, something went wrong.
status: Open [ 1 ] => In Progress [ 3 ]
Commented by: @cincuranet
It's a change in Embedded server behavior. The 2.5 version will change this completely (to be solved).
Me and Dmitry conclude, that we'll try to solve this on both sides, to see where it will be easier.
Link: This issue relate to CORE1851 [ CORE1851 ]
Fixed in 2.1.1 version of FB server.
status: In Progress [ 3 ] => Closed [ 6 ]
resolution: Won't Fix [ 2 ]
cincuranet
No branches or pull requests
Submitted by: @cincuranet
Relate to CORE1851
Test case:
FbConnectionStringBuilder builder = new FbConnectionStringBuilder();
builder.Database = "test";
builder.ServerType = FbServerType.Embedded;
builder.UserID = "SYSDBA";
builder.Password = "masterkey";
<//builder.Pooling> = false;
FbConnection.CreateDatabase(builder.ToString(), true);
new FbConnection(builder.ToString()).Open();
and the application freezes at the end. Uncommenting the line solves the problem. The 2.0.3 version is OK.
The text was updated successfully, but these errors were encountered: