Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
| Dev |
|
| QA |
|
| Priority | Minor |
| Complexity | Unknown |
| Component | Tools - Table Data Editor |
| Version | 15.0 |
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.
We fixed this for postgres in version 15 and 16. I need to go through and check to see if this setting is the same in postgres variant type databases. If so, we should do the same for each one.
Greenplum, paraccel, redshift, netezza, ncluster, mysql are possible databases to check...
Only database that was also affected by this database property is greenplum. The needed changes have been made so that greenplum will also correctly pull this value from the database.
Only database that was also affected by this database property is greenplum. The needed changes have been made so that greenplum will also correctly pull this value from the database.
Issue #13087 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build v16.0.0-beta-6 |
| No time estimate |
1 issue link |
relates to #13085
Issue #13085Table Data Editor on PostgreSQL should check "show standard_conforming_strings" in ConnectionProperties.requiresEscapeBackslash() |
We fixed this for postgres in version 15 and 16. I need to go through and check to see if this setting is the same in postgres variant type databases. If so, we should do the same for each one.
Greenplum, paraccel, redshift, netezza, ncluster, mysql are possible databases to check...