Re: Question on inserting non-ascii strings

From: Sam Mason <sam(at)samason(dot)me(dot)uk>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Question on inserting non-ascii strings
Date: 2009-05-14 18:15:12
Message-ID: 20090514181512.GI22221@samason.me.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 14, 2009 at 01:57:04PM -0400, Steven Lembark wrote:
> On Thu, 14 May 2009 18:44:57 +0100 Sam Mason <sam(at)samason(dot)me(dot)uk> 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 and everything should just work. Unfortunately I
> > don't use Perl much, so can't give much in the way of a demo--hopefully
> > others will.
>
> That is what I thought should happen, but
> using a database with encoding of UTF8 and
> client_encoding of UTF8 still gave me the
> warnings.

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?

--
Sam http://samason.me.uk/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-05-14 18:45:07 Re: work_mem greater than 2GB issue
Previous Message Raymond O'Donnell 2009-05-14 18:14:20 Re: how to extract data from bytea so it is be used in blob for mysql database