[
https://issues.apache.org/jira/browse/FLINK-39424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Nuyanzin updated FLINK-39424:
------------------------------------
Fix Version/s: 1.20.4
> Setting LIKE does not support default escape characters.
> --------------------------------------------------------
>
> Key: FLINK-39424
> URL: https://issues.apache.org/jira/browse/FLINK-39424
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Planner
> Affects Versions: 2.3.0
> Reporter: Qilong Wang
> Assignee: Qilong Wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.4, 2.1.2, 2.3.0, 2.4.0
>
>
> In standard SQL, the LIKE clause does not have default escape characters,
> such as the following:
> * MySQL and PostgreSQL: These systems typically default to using backslashes
> as string literals and escape characters in Like clauses. However, it is
> generally not recommended to rely on this default setting as it can be
> changed through server configuration (such as NOACKSLASH-ESCAPES in MySQL or
> standard_comforming_strings in Postgres).
> * SQL Server (MS-DOS): There are no default escape characters. You must use
> the ESCAPE clause. Alternatively, SQL Server allows you to escape wildcard
> characters by enclosing them in square brackets (e.g. LIKE'20 [_]% ').
> * Oracle and SQLite: There are no default escape characters. If you need to
> escape wildcard characters, you must explicitly define an escape character
> using the ESCAPE clause.
> Considering that our string literal also does not support backslashes, and
> default escape characters may cause confusion, we have chosen to set it to
> not support default escape characters.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
