Re: Why don't I get a LATIN1 encoding here with SET ENCODING? - Mailing list pgsql-sql

From Bryce Nesbitt
Subject Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
Date
Msg-id 4AF0FAF9.8080306@obviously.com
Whole thread Raw
In response to Re: Why don't I get a LATIN1 encoding here with SET ENCODING?  (Craig Ringer <craig@postnewspapers.com.au>)
Responses Re: Why don't I get a LATIN1 encoding here with SET ENCODING?  (Craig Ringer <craig@postnewspapers.com.au>)
Re: Why don't I get a LATIN1 encoding here with SET ENCODING?  (Craig Ringer <craig@postnewspapers.com.au>)
List 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.



pgsql-sql by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
Next
From: Craig Ringer
Date:
Subject: Re: Why don't I get a LATIN1 encoding here with SET ENCODING?