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

Поиск
Список
Период
Сортировка
От Bryce Nesbitt
Тема Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
Дата
Msg-id 4AF0FAF9.8080306@obviously.com
обсуждение исходный текст
Ответ на 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>)
Re: Why don't I get a LATIN1 encoding here with SET ENCODING?  (Craig Ringer <craig@postnewspapers.com.au>)
Список 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 по дате отправления:

Предыдущее
От: Craig Ringer
Дата:
Сообщение: Re: Why don't I get a LATIN1 encoding here with SET ENCODING?
Следующее
От: Craig Ringer
Дата:
Сообщение: Re: Why don't I get a LATIN1 encoding here with SET ENCODING?