Issue Details (XML | Word | Printable)

Key: JDBC-584
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Mark Rotteveel
Reporter: Mark Rotteveel
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Jaybird JCA/JDBC Driver

Some connection properties don't work from DriverManager

Created: 07/May/19 02:55 PM   Updated: 25/May/19 10:03 AM
Component/s: JDBC driver
Affects Version/s: Jaybird 2.2.13, Jaybird 3.0.0, Jaybird 3.0.1, Jaybird 3.0.2, Jaybird 3.0.3, Jaybird 2.2.14, Jaybird 3.0.4, Jaybird 3.0.5, Jaybird 2.2.15, Jaybird 4.0.0-beta-1
Fix Version/s: Jaybird 3.0.6, Jaybird 4.0.0-beta-2, Jaybird 4


 Description  « Hide
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)

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel made changes - 07/May/19 02:56 PM
Field Original Value New Value
Fix Version/s Jaybird 3.0.6 [ 10883 ]
Fix Version/s Jaybird 4.0.0-beta-2 [ 10902 ]
Fix Version/s Jaybird 4 [ 10441 ]
Mark Rotteveel made changes - 07/May/19 03:29 PM
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)
Mark Rotteveel made changes - 07/May/19 04:08 PM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Mark Rotteveel made changes - 25/May/19 10:03 AM
Status Resolved [ 5 ] Closed [ 6 ]