From: Michael Glaesemann <grzm@seespotcode.net>
To: Paul Lambert <paul.lambert@autoledgers.com.au>
Cc: pgsql-sql@postgresql.org
Subject: Re: Using escape strings in an insert statement.
Date: Mon, 2 Jul 2007 19:13:12 -0500
Message-ID: <3D8C02A5-AF50-4D0C-AF36-188C83980452@seespotcode.net> (raw)
In-Reply-To: <468989C0.7020601@autoledgers.com.au>
References: <46898000.7030601@autoledgers.com.au>
<B98511E0-E97F-4B76-82F0-CE92FC2ACA07@seespotcode.net>
<468989C0.7020601@autoledgers.com.au>
On Jul 2, 2007, at 18:26 , Paul Lambert wrote:
> Looks like it's a toss-up between turning
> standard_conforming_strings on or turning escape_string_warning
> off, both seem to have the same effect in not giving the error
> anymore.
A warning is not an error :)
Michael Glaesemann
grzm seespotcode net
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: grzm@seespotcode.net, paul.lambert@autoledgers.com.au
Subject: Re: Using escape strings in an insert statement.
In-Reply-To: <3D8C02A5-AF50-4D0C-AF36-188C83980452@seespotcode.net>
* 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