We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
*Issue migrated from trac ticket # 877 www.kunlunbase.com *
component: computing nodes | priority: major
sql code: set escape_string_warning = off; set standard_conforming_strings = on; select 'a\bcd' as f1, 'a\b*cd' as f2, 'a\b**cd' as f3, 'abcd' as f4, 'ab*cd' as f5, '\' as f6; ERROR: syntax error at or near "\" LINE 1: ...cd' as f2, 'a\b*''cd' as f3, 'abcd\' as f4, 'ab\*cd' as ... pg中的输出: f1 | f2 | f3 | f4 | f5 | f6 -------+--------+---------+-------+--------+---- a\bcd | a\b'cd | a\b''cd | abcd\ | ab\'cd | \\ (1 row) set standard_conforming_strings = off; select 'a\\bcd' as f1, 'a\\b\'cd' as f2, 'a\\b\'''cd' as f3, 'abcd\\' as f4, 'ab\\\'cd' as f5, '\\\\' as f6; f1 | f2 | f3 | f4 | f5 | f6 -------+--------+---------+-------+--------+---- a\bcd | a\b'cd | a\b''cd | abcd\ | ab\'cd | \\ (1 row)
sql code: set escape_string_warning = off; set standard_conforming_strings = on;
select 'a\bcd' as f1, 'a\b*cd' as f2, 'a\b**cd' as f3, 'abcd' as f4, 'ab*cd' as f5, '\' as f6;
ERROR: syntax error at or near "\" LINE 1: ...cd' as f2, 'a\b*''cd' as f3, 'abcd\' as f4, 'ab\*cd' as ...
pg中的输出:
f1 | f2 | f3 | f4 | f5 | f6 -------+--------+---------+-------+--------+---- a\bcd | a\b'cd | a\b''cd | abcd\ | ab\'cd | \\ (1 row)
set standard_conforming_strings = off;
select 'a\\bcd' as f1, 'a\\b\'cd' as f2, 'a\\b\'''cd' as f3, 'abcd\\' as f4, 'ab\\\'cd' as f5, '\\\\' as f6;
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
No branches or pull requests
*Issue migrated from trac ticket # 877 www.kunlunbase.com *
component: computing nodes | priority: major
2022-07-05 16:53:08: vito@zettadb.com created the issue
The text was updated successfully, but these errors were encountered: