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

DatabaseMetaData patterns: treat escape character as normal when not followed by _, % or itself. [JDBC562] #595

Closed
firebird-automations opened this issue Oct 30, 2018 · 5 comments

Comments

@firebird-automations
Copy link

Submitted by: @mrotteveel

Relate to JDBC559

Metadata patterns in JDBC are derived from ODBC, and ODBC specifies with regard to the escape:

"""
An escape character, which is driver-specific and is used to include underscores, percent signs, and the escape character as literals. If the escape character precedes a non-special character, the escape character has no special meaning. If the escape character precedes a special character, it escapes the special character. For example, "\a" would be treated as two characters, "\" and "a", but "\%" would be treated as the non-special single character "%".
"""
(from: https://docs.microsoft.com/en-us/sql/odbc/reference/develop-app/pattern-value-arguments?view=sql-server-2017)

An escape followed by a non-special is currently not handled correctly, this needs to be fixed.

See also JDBC559.

Commits: ff8fde4

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Link: This issue relate to JDBC559 [ JDBC559 ]

@firebird-automations
Copy link
Author

Commented by: @mrotteveel

Don't forget to change SqlLikeMatcher as well (and consider renaming to MetadataPatternMatcher).

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

Fix Version: Jaybird 4 [ 10441 ]

@firebird-automations
Copy link
Author

Modified by: @mrotteveel

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

@firebird-automations
Copy link
Author

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
Development

No branches or pull requests

2 participants