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

Some connection properties don't work from DriverManager [JDBC584] #615

Closed
firebird-issue-importer opened this issue May 7, 2019 · 5 comments

Comments

@firebird-issue-importer
Copy link

@firebird-issue-importer firebird-issue-importer commented May 7, 2019

Submitted by: @mrotteveel

It looks like an overhaul of the connection properties implementation in 2004 (for JayBird 1.5.2(?)) broke connection properties that are not associated with a DPB item, but just have a name in FBConnectionProperties for DriverManager connections. It works correctly for datasource connections.

As far as I can tell, the only affected property is defaultIsolation/isolation (and in theory also database and type, but those are handled differently and should not be settable this way)

Commits: 7479071 08fab5c 81f49ec

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 7, 2019

Modified by: @mrotteveel

Fix Version: Jaybird 3.0.6 [ 10883 ]

Fix Version: Jaybird 4.0.0-beta-2 [ 10902 ]

Fix Version: Jaybird 4 [ 10441 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 7, 2019

Modified by: @mrotteveel

description: It looks like an overhaul of the connection properties implementation in 2004 broke connection properties that are not associated with a DPB item, but just have a name in FBConnectionProperties for DriverManager connections. It works correctly for datasource connections.

As far as I can tell, the only affected property is defaultIsolation/isolation (and in theory also database and type, but those are handled differently and should not be settable this way)

=>

It looks like an overhaul of the connection properties implementation in 2004 (for JayBird 1.5.2(?)) broke connection properties that are not associated with a DPB item, but just have a name in FBConnectionProperties for DriverManager connections. It works correctly for datasource connections.

As far as I can tell, the only affected property is defaultIsolation/isolation (and in theory also database and type, but those are handled differently and should not be settable this way)

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 7, 2019

Commented by: @mrotteveel

Fixed in 3.0.6 and 4.0.0-beta-2

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 7, 2019

Modified by: @mrotteveel

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

resolution: Fixed [ 1 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented May 25, 2019

Modified by: @mrotteveel

status: Resolved [ 5 ] => Closed [ 6 ]

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