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
Add support for url encoded connection properties [JDBC604] #635
Comments
Modified by: @mrotteveelFix Version: Jaybird 4.0.0-beta-2 [ 10902 ] Fix Version: Jaybird 3.0.9 [ 10917 ] Fix Version: Jaybird 4 [ 10441 ] |
Modified by: @mrotteveel |
Modified by: @mrotteveeldescription: Due to JDBC603 we need to implement support for URL-encoding of the connection properties in a connection string, so that for example `;` can be used in a connection property in a connection string. This will introduce a minor backwards compatibility issues, because both + and % in a connection property will need to be escaped (with %25 and %2B). => Due to JDBC603 we need to implement support for URL-encoding of the connection properties in a connection string, so that for example `;` can be used in a connection property in a connection string. This will introduce a minor backwards compatibility issues, because both + and % in a connection property will need to be escaped (with %25 and %2B). The implementation will use UTF-8 for decoding escaped values. |
Modified by: @mrotteveeldescription: Due to JDBC603 we need to implement support for URL-encoding of the connection properties in a connection string, so that for example `;` can be used in a connection property in a connection string. This will introduce a minor backwards compatibility issues, because both + and % in a connection property will need to be escaped (with %25 and %2B). The implementation will use UTF-8 for decoding escaped values. => Due to JDBC603 we need to implement support for URL-encoding of the connection properties in a connection string, so that for example `;` can be used in a connection property in a connection string. This will introduce a minor backwards compatibility issues, because both + and % in a connection property will need to be escaped (with %2B and %25). The implementation will use UTF-8 for decoding escaped values. |
Commented by: @mrotteveel Implemented. |
Modified by: @mrotteveelstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @mrotteveel
Block progress on JDBC603
Due to JDBC603 we need to implement support for URL-encoding of the connection properties in a connection string, so that for example `;` can be used in a connection property in a connection string.
This will introduce a minor backwards compatibility issues, because both + and % in a connection property will need to be escaped (with %2B and %25).
The implementation will use UTF-8 for decoding escaped values.
Commits: 3de4e4a 4336e06
The text was updated successfully, but these errors were encountered: