On Thu, May 14, 2009 at 07:39:41PM -0400, Steven Lembark wrote:
>
> > Which "warnings" are you talking about? I thought you said you had
> > plain SQL working OK, but were struggling to pass parameters containing
> > UTF-8 encoded characters.
> >
> > Are you sure that your Perl code is passing t
> Which "warnings" are you talking about? I thought you said you had
> plain SQL working OK, but were struggling to pass parameters containing
> UTF-8 encoded characters.
>
> Are you sure that your Perl code is passing the string encoded as UTF8?
Excellent point: Perl will only pass through the
On Thu, May 14, 2009 at 01:57:04PM -0400, Steven Lembark wrote:
> On Thu, 14 May 2009 18:44:57 +0100 Sam Mason wrote:
> > You want to be using whatever language you're generating the parameter
> > from (Perl) to handle the expansion of escape sequences for you. This
> > will cause the expanded st
On Thu, 14 May 2009 18:44:57 +0100
Sam Mason wrote:
> You want to be using whatever language you're generating the parameter
> from (Perl) to handle the expansion of escape sequences for you. This
> will cause the expanded string (i.e. the escapes have been interpreted)
> to be sent to Postgres
On Thu, May 14, 2009 at 11:25:33AM -0400, Steven Lembark wrote:
> Q: Is there any combination of locale, encoding,
>client_encoding or functions that will allow
>me to insert values with these escape sequences
>without getting the warnings?
>
> Trying this in psql with various combina
Using Postgres 8.3 with DBI 1.607, DBD::Pg 2.12.0, perl v5.10.0,
I am trying to insert the medline database
contents, which include non-ascii char's,
hopefully using a prepared query.
Playing with the locale, encoding,
client_encoding, standard_conforming_strings,
leaves me able to insert val
