You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For compatibility with systems which may have changed the default LIKE-clause escape-character, sometimes it will be specified explicitly:
SELECT*FROM information_schema WHERE
table_name LIKE'd\_%' ESCAPE '\' AND table_schema IN ('chapow_core')
Despite the syntax highlighting you may see above indicating there's an un-terminated string, you'll note from this SQL Fiddle that Postgres does not treat the backslash as an escape-character within the string, and therefore does not hit a syntax-error. This behavior may be different from generic SQL.
I'm happy to submit test and modifications using a patch or pull-request if you'll take it.
Cheers.
The text was updated successfully, but these errors were encountered:
koyae
added a commit
to koyae/migration
that referenced
this issue
Mar 6, 2018
…or Postgres to prevent incorrect highlighting under WHERE LIKE ESCAPE where the escape-character is a backslash (probably not the only possible usecase, note). More detail at exu/pgsql.vim#17. If that's fixed centrally I should include the file via pathogen but this works for now.
For compatibility with systems which may have changed the default LIKE-clause escape-character, sometimes it will be specified explicitly:
Despite the syntax highlighting you may see above indicating there's an un-terminated string, you'll note from this SQL Fiddle that Postgres does not treat the backslash as an escape-character within the string, and therefore does not hit a syntax-error. This behavior may be different from generic SQL.
I'm happy to submit test and modifications using a patch or pull-request if you'll take it.
Cheers.
The text was updated successfully, but these errors were encountered: