Table Data Editor on PostgreSQL should check "show standard_conforming_strings" in ConnectionProperties.requiresEscapeBackslash().
You can use the "show standard_conforming_strings" or "set standard_conforming_strings = on"
From the PostgreSQL documentation :
http://www.postgresql.org/docs/current/static/runtime-config-compatible.html
This controls whether ordinary string literals ('...') treat backslashes literally, as specified in the SQL standard. Beginning in PostgreSQL 9.1, the default is on (prior releases defaulted to off). Applications can check this parameter to determine how string literals will be processed. The presence of this parameter can also be taken as an indication that the escape string syntax (E'...') is supported. Escape string syntax (Section 4.1.2.2) should be used if an application desires backslashes to be treated as escape characters.
Field | Old Value | New Value |
---|---|---|
Description | Table Data Editor on PostgreSQL should check "show standard_conforming_strings" in ConnectionProperties.requiresEscapeBackslash(). You can use the "show standard_conforming_strings" or "set standard_conforming_strings = on"
From the PostgreSQL documentation :
|
Table Data Editor on PostgreSQL should check "show standard_conforming_strings" in ConnectionProperties.requiresEscapeBackslash(). You can use the "show standard_conforming_strings" or "set standard_conforming_strings = on"
From the PostgreSQL documentation :
|
Field | Old Value | New Value |
---|---|---|
Dev Assignee | SachinPrakash (Sachin Prakash) | ivangron (Ivan Gron) |
Field | Old Value | New Value |
---|---|---|
Fixed Build | v15.0.14-4, v16.0.0-beta-6 | |
Resolution | Fixed | |
Resolved Date | Feb 13, 2015 12:04 AM | |
Status | New | Resolved |
Field | Old Value | New Value |
---|---|---|
Status | Resolved | Verified |
Field | Old Value | New Value |
---|---|---|
Resolution | Fixed | Incomplete |
Resolved Date | Feb 13, 2015 12:04 AM | |
Status | Verified | Reopened |
Field | Old Value | New Value |
---|---|---|
Resolution | Incomplete | Fixed |
Resolved Date | Feb 16, 2015 5:49 PM | |
Status | Reopened | Resolved |
Field | Old Value | New Value |
---|---|---|
Status | Resolved | Verified |
Field | Old Value | New Value |
---|---|---|
Status | Verified | Closed |
Issue #13085 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build v15.0.14-4, v16.0.0-beta-6 |
No time estimate |
4 issue links |
relates to #13087
Issue #13087Table Data Editor on PostgreSQL type databases may need to check "show standard_conforming_strings" in ConnectionProperties.requiresEscapeBackslash() |
relates to #13116
Issue #13116Importing data to new table in PostgreSQL will open many new connections |
relates to #13810
Issue #13810Export tool for PostgreSQL is not escaping "\" in strings |
breaks #13116
Issue #13116Importing data to new table in PostgreSQL will open many new connections |