| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Andy Anderson" <aanderson(at)amherst(dot)edu> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Quoting " |
| Date: | 2008-04-30 15:52:39 |
| Message-ID: | dcc563d10804300852r7721a7e3q5cb6bb0cf5b83441@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-general |
On Wed, Apr 30, 2008 at 7:10 AM, Andy Anderson <aanderson(at)amherst(dot)edu> wrote:
> In a test I just did, the sequence \" (backslash double-quote) is
> interpreted as just a " inside of the E'...' string constant expression.
> This is great, since PHP's addslashes() sticks them in along with the other
> stuff I really need to quote like ' and \. But I see that \" isn't
> documented in the manual in section 4.1.2.1. I assume this is, in fact,
> standard behavior for Postgres? (Perhaps a comprehensive table might be a
> good idea at this point in the manual.)
Why are you using php's addslashes() function? Is there something
missing from pg_escape_string()??? Or are you doing something else
I'm not thinking of?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Anderson | 2008-04-30 16:51:45 | Re: Quoting " |
| Previous Message | Andy Anderson | 2008-04-30 14:33:19 | Re: Quoting " |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-04-30 16:13:15 | Re: Why is postgres autovacuuming a table that is never updated? |
| Previous Message | Joseph S | 2008-04-30 15:52:09 | Re: Why is postgres autovacuuming a table that is never updated? |