From: | Vick Khera <vivek(at)khera(dot)org> |
---|---|
To: | tuanhoanganh <hatuan05(at)gmail(dot)com> |
Cc: | Ivan Voras <ivoras(at)freebsd(dot)org>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Bytea error in PostgreSQL 9.0 |
Date: | 2010-12-14 16:34:00 |
Message-ID: | AANLkTink4krh2kperDJc4PG-Vmh3ZqOLbWsvdTswNz8n@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Dec 14, 2010 at 11:22 AM, tuanhoanganh <hatuan05(at)gmail(dot)com> wrote:
> Thanks for your answer. But I don't want to change db config or ALTER
> DATABASE data SET bytea_output='escape';
> I can change my app. So is there document introduce how to work with
> postgresql 9 bytea
Your .Net or whatever library you're using will need to learn how to
interpret the new encoding, and do the necessary work to make the data
represented to you what you expect.
I use perl DBD::Pg interface, and the current released version does
not know how to do it, so I had to write my own layer of code into my
ORM that detects and decodes the new bytea format before passing it
back to my app. The postgres manual has many details that will help
you do something like this.
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Figueiredo Jr. | 2010-12-14 16:36:35 | Re: Bytea error in PostgreSQL 9.0 |
Previous Message | Tom Lane | 2010-12-14 16:30:53 | Re: Bytea error in PostgreSQL 9.0 |