Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You probably want to use <a href="http://www.postgresql.org/docs/current/static/functions-string.html" rel="nofollow"><code>replace</code></a>:</p> <pre><code>SELECT REPLACE(text, '"', E'\\"') FROM aTable WHERE ... </code></pre> <p>You'll need to escape your escape character to get a literal backslash (hence the doubled backslash) and use the "E" prefix on the replacement string to get the right <a href="http://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#SQL-SYNTAX-STRINGS-ESCAPE" rel="nofollow">escape syntax</a>.</p> <p><strong>UPDATE</strong>: And thanks to a_horse_with_no_name's usual strictness (a good thing BTW), we have a solution that doesn't need the extra backslash or non-standard "E" prefix:</p> <pre><code>set standard_conforming_strings = on; SELECT REPLACE(text, '"', '\"') FROM aTable WHERE ... </code></pre> <p>The <a href="http://www.postgresql.org/docs/current/static/runtime-config-compatible.html#GUC-STANDARD-CONFORMING-STRINGS" rel="nofollow"><code>standard_conforming_strings</code></a> option tells PostgreSQL to use standard syntax for SQL strings:</p> <blockquote> <p>This controls whether ordinary string literals ('...') treat backslashes literally, as specified in the SQL standard.</p> </blockquote> <p>This would also impact your <a href="http://www.postgresql.org/docs/9.0/interactive/sql-syntax-lexical.html#SQL-BACKSLASH-TABLE" rel="nofollow"><code>\x5C</code> escape</a>:</p> <blockquote> <p>If the configuration parameter standard_conforming_strings is off, then PostgreSQL recognizes backslash escapes in both regular and escape string constants. This is for backward compatibility with the historical behavior, where backslash escapes were always recognized.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POEscaping quotes inside text when dumping Postgres Sql
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmu is too short
    1. USmu is too short
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POEscaping quotes inside text when dumping Postgres Sql
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COUsing the backslash that way is deprecated. It is highly recommended to use `standard_conforming_strings = on` which will be the default in the next release if I'm not mistaken. http://www.postgresql.org/docs/9.0/static/runtime-config-compatible.html#GUC-STANDARD-CONFORMING-STRINGS
      singulars
      1. PO
      1. USa_horse_with_no_name
    2. CO@a_horse_with_no_name: What's the best way to get a `\` in a string that works in PostgreSQL 8 and 9 without producing any warnings and doesn't care about the `standard_conforming_strings` setting? A lot of people (including me) have to deal with both 8 and 9 and many (such as Heroku users) don't have full control over the PostgreSQL configuration.
      singulars
      1. PO
      1. USmu is too short
    3. CO@mu is too short: getting a single quote `'` into a string is easy: simply put two quotes into the string: `'Peter''s bike'`. That is unaffacted by the standard_conforming_strings. The same is true for a double quote: `'12" Inch'` standard_conforming_strings is **only** about using a backslash in the literal
      singulars
      1. PO
      1. USa_horse_with_no_name
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload