Re: Why don't I get a LATIN1 encoding here with SET ENCODING?

From: Bryce Nesbitt <bryce2(at)obviously(dot)com>
To: pgsql-sql(at)postgresql(dot)org
Cc: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
Subject: Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
Date: 2009-11-04 03:54:33
Message-ID: 4AF0FAF9.8080306@obviously.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Craig Ringer wrote:
> Yes - but you are *not* presenting a Latin-1 character. You're
> presenting four Latin-1 characters:
>
> '\', '3', '7', '5'
Well, then I have a different question. If I can view a bytea column as so:

> select object from context_objects where context_key=100041;
object
-----------------------------
\005\007\021\007Article\003
(1 row)

How can I modify the data and put it back into the column?

I'm trying to track down while a ten year old system no longer works
after a Perl DBI upgrade. Something is munging high LATIN1. The DB
itself is UTF-8, client_encoding is set to LATIN1. We expect LATIN1 in,
same stuff out. But right now that is what I'm debugging.

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Craig Ringer 2009-11-04 04:25:41 Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
Previous Message Craig Ringer 2009-11-04 03:47:21 Re: Why don't I get a LATIN1 encoding here with SET ENCODING?