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

Add support for url encoded connection properties [JDBC604] #635

Closed
firebird-issue-importer opened this issue Dec 8, 2019 · 7 comments
Closed

Comments

@firebird-issue-importer
Copy link

@firebird-issue-importer firebird-issue-importer commented Dec 8, 2019

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 8, 2019

Modified by: @mrotteveel

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

Fix Version: Jaybird 3.0.9 [ 10917 ]

Fix Version: Jaybird 4 [ 10441 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 8, 2019

Modified by: @mrotteveel

Link: This issue block progress on JDBC603 [ JDBC603 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 8, 2019

Modified by: @mrotteveel

description: 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.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 8, 2019

Modified by: @mrotteveel

description: 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.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 8, 2019

Commented by: @mrotteveel

Implemented.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 8, 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 Jan 19, 2020

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
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants