Issue Details (XML | Word | Printable)

Key: JDBC-627
Type: Improvement Improvement
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 JDBC Driver

Expose option to merge properties

Created: 28/Jun/20 09:42 AM   Updated: 11/Aug/20 02:38 PM
Component/s: JDBC driver
Affects Version/s: Jaybird 2.2.15, Jaybird 4.0.0, Jaybird 3.0.9
Fix Version/s: Jaybird 4.0.1, Jaybird 3.0.10, Jaybird 5


 Description  « Hide
Prior to Jaybird 2.2.10, it was possible to call FBDriverPropertyManager.normalize(String url, Map props) to merge and normalize the properties from a map/properties object and the JDBC url. When fixing JDBC-421 the parsing and merging was moved into FBDriver, while only the normalization remained in FBDriverPropertyManager. Since 2.2.10, the url parameter was ignored, and since 3.0.0 this parameter was removed and access level of FBDriverPropertyManager was downgraded to default.

Red Soft relies on this method to combine properties before using them in their custom data source implementation, and would like the old behaviour, or the equivalent thereof, to be available.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Mark Rotteveel made changes - 28/Jun/20 09:42 AM
Field Original Value New Value
Fix Version/s Jaybird 4.0.1 [ 10921 ]
Fix Version/s Jaybird 3.0.10 [ 10932 ]
Fix Version/s Jaybird 5 [ 10871 ]
Mark Rotteveel made changes - 28/Jun/20 09:56 AM
Description Prior to Jaybird 2.2.10, it was possible to call FBDriverPropertyManager.normalize(String url, Map props) to merge and normalize the properties from a map/properties object and the JDBC url. When fixing JDBC-421 the parsing and merging was moved into FBDriver, while only the normalization remained in FBDriverPropertyManager. Since 2.2.10, the url parameter was ignored, and since 3.0.0 this parameter was removed.

Red Soft relies on this method to combine properties before using them in their custom data source implementation, and would like the old behaviour or the equivalent thereof the be availab.e
Prior to Jaybird 2.2.10, it was possible to call FBDriverPropertyManager.normalize(String url, Map props) to merge and normalize the properties from a map/properties object and the JDBC url. When fixing JDBC-421 the parsing and merging was moved into FBDriver, while only the normalization remained in FBDriverPropertyManager. Since 2.2.10, the url parameter was ignored, and since 3.0.0 this parameter was removed and access level of FBDriverPropertyManager was downgraded to default.

Red Soft relies on this method to combine properties before using them in their custom data source implementation, and would like the old behaviour or the equivalent thereof the be available.
Mark Rotteveel made changes - 28/Jun/20 12:19 PM
Description Prior to Jaybird 2.2.10, it was possible to call FBDriverPropertyManager.normalize(String url, Map props) to merge and normalize the properties from a map/properties object and the JDBC url. When fixing JDBC-421 the parsing and merging was moved into FBDriver, while only the normalization remained in FBDriverPropertyManager. Since 2.2.10, the url parameter was ignored, and since 3.0.0 this parameter was removed and access level of FBDriverPropertyManager was downgraded to default.

Red Soft relies on this method to combine properties before using them in their custom data source implementation, and would like the old behaviour or the equivalent thereof the be available.
Prior to Jaybird 2.2.10, it was possible to call FBDriverPropertyManager.normalize(String url, Map props) to merge and normalize the properties from a map/properties object and the JDBC url. When fixing JDBC-421 the parsing and merging was moved into FBDriver, while only the normalization remained in FBDriverPropertyManager. Since 2.2.10, the url parameter was ignored, and since 3.0.0 this parameter was removed and access level of FBDriverPropertyManager was downgraded to default.

Red Soft relies on this method to combine properties before using them in their custom data source implementation, and would like the old behaviour, or the equivalent thereof, to be available.
Mark Rotteveel added a comment - 28/Jun/20 02:22 PM
Implemented for 3.0.10, 4.0.1 and 5.

Mark Rotteveel made changes - 28/Jun/20 02:22 PM
Status Open [ 1 ] Resolved [ 5 ]
Resolution Fixed [ 1 ]
Mark Rotteveel made changes - 11/Aug/20 02:38 PM
Status Resolved [ 5 ] Closed [ 6 ]