Message-ID: <45D023A0.3040601@archonet.com>
Date: Mon, 12 Feb 2007 08:21:52 +0000
From: Richard Huxton <dev@archonet.com>
User-Agent: IceDove 1.5.0.9 (X11/20061220)
MIME-Version: 1.0
To: Paul Lambert <paul.lambert@autoledgers.com.au>
Cc: Phillip Smith <phillip.smith@weatherbeeta.com.au>,
	'Joe' <dev@freedomcircle.net>, pgsql-sql@postgresql.org
Subject: Re: COPY FROM query.
References: <00d601c74e3f$5fc59940$9b0014ac@wbaus090>
	<45CFBA1F.9090109@autoledgers.com.au>
In-Reply-To: <45CFBA1F.9090109@autoledgers.com.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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