From: | "Tomasz Rejman" <tr(at)ideo(dot)pl> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Selecting data from bytea field in 8.3 |
Date: | 2009-05-12 07:30:12 |
Message-ID: | BABE03B9B20A4281B7D26D36DCED5090@pc53TRejman |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi there.
Few days ago I have changed my postgreSQL to 8.3 version and I have problem
with bytea fields. Let me show you an example:
CREATE TABLE testtable
(
test bytea
);
insert into testTable (test) VALUES
(E'\304\205\304\207\305\274\303\263\305\202wjfdsafdsa');
select encode(test, 'escape') from testTable;
In the previous version last Select will display exact characters in UTF8
encoding (some polish letters with dot-s and comma-s on them), but in 8.3
i'm getting an escaped string with byte codes (like this one in Insert
querry)
(correct data should be like that:
select E'\304\205\304\207\305\274\303\263\305\202wjfdsafdsa';
)
What should I do to tell the postgreSQL to unescape that data?
because I cant add an E letter to column name.
Something like that:
Select E test;
btw. I know that bytea field should be used for binary data, but this is
only an example.
I'm using this type of field in my functions to encrypt/decrypt some data
and i need to use set_byte()/get_byte() functions.
--
Tomasz Rejman
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2009-05-12 07:55:13 | Re: Unable to access table named "user" |
Previous Message | Joe Kramer | 2009-05-12 07:26:32 | Unable to access table named "user" |