| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Paul Lambert <paul(dot)lambert(at)autoledgers(dot)com(dot)au> |
| Cc: | Phillip Smith <phillip(dot)smith(at)weatherbeeta(dot)com(dot)au>, 'Joe' <dev(at)freedomcircle(dot)net>, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: COPY FROM query. |
| Date: | 2007-02-12 08:21:52 |
| Message-ID: | 45D023A0.3040601@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Paul Lambert wrote:
> Phillip Smith wrote:
>> "Having said that, if I switch it to a forward slash it works without
>> error... odd, given that weenblows standard is backslash."
>>
>> Yes, but PostgreSQL uses a back-slash as an escape character, which
>> needs to
>> be used to escape itself at an application level before the O/S gets
>> to deal
>> with it :)
>
> OK, that makes sense, cheers for the help.
Almost correct - PG is moving over to a more SQL standards-based
interpretation of what should be done with backslashes in strings. The
old behaviour will still be available by prefixing a string with E -
E'like this'.
See manuals for details.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ezequias Rodrigues da Rocha | 2007-02-12 15:41:10 | Sum sets of records |
| Previous Message | Richard Huxton | 2007-02-12 08:19:15 | Re: [SQL] Password Policy |