From: Richard Huxton <dev@archonet.com>
To: Paul Lambert <paul.lambert@autoledgers.com.au>
Cc: Phillip Smith <phillip.smith@weatherbeeta.com.au>
Cc: Joe <dev@freedomcircle.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: COPY FROM query.
Date: Mon, 12 Feb 2007 08:21:52 +0000
Message-ID: <45D023A0.3040601@archonet.com> (raw)
In-Reply-To: <45CFBA1F.9090109@autoledgers.com.au>
References: <00d601c74e3f$5fc59940$9b0014ac@wbaus090>
<45CFBA1F.9090109@autoledgers.com.au>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: dev@archonet.com, paul.lambert@autoledgers.com.au, phillip.smith@weatherbeeta.com.au, dev@freedomcircle.net
Subject: Re: COPY FROM query.
In-Reply-To: <45D023A0.3040601@archonet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox