From: Bryce Nesbitt <bryce2@obviously.com>
To: pgsql-sql@postgresql.org
Cc: Craig Ringer <craig@postnewspapers.com.au>
Subject: Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
Date: Tue, 03 Nov 2009 19:54:33 -0800
Message-ID: <4AF0FAF9.8080306@obviously.com> (raw)
In-Reply-To: <4AF0F949.3060807@postnewspapers.com.au>
References: <4AF0D531.5080309@obviously.com>
<4AF0E70F.1030201@postnewspapers.com.au>
<4AF0F6A7.7070505@obviously.com>
<4AF0F949.3060807@postnewspapers.com.au>
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.
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: bryce2@obviously.com, craig@postnewspapers.com.au
Subject: Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
In-Reply-To: <4AF0FAF9.8080306@obviously.com>
* 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