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
Expose option to merge properties [JDBC627] #657
Comments
Modified by: @mrotteveelFix Version: Jaybird 4.0.1 [ 10921 ] Fix Version: Jaybird 3.0.10 [ 10932 ] Fix Version: Jaybird 5 [ 10871 ] |
Modified by: @mrotteveeldescription: 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 JDBC421 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 JDBC421 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. |
Modified by: @mrotteveeldescription: 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 JDBC421 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 JDBC421 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. |
Commented by: @mrotteveel Implemented for 3.0.10, 4.0.1 and 5. |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @mrotteveel
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 JDBC421 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.
Commits: 69a69bb 195d6ae 7f2ca32 bd9c022 725e314 a3088a9
The text was updated successfully, but these errors were encountered: