From: Bart Degryse <Bart.Degryse@indicator.be>
To: Ragnar <gnari@hive.is>
Cc: pgsql-sql@postgresql.org
Subject: Re: UNICODE and PL/PGSQL
Date: Mon, 27 Nov 2006 15:54:47 +0100
Message-ID: <456B0A47020000300000FC1E@webaccess.indicator.be> (raw)
In-Reply-To: <1164638251.27070.45.camel@localhost.localdomain>
References: <456AD17A020000300000FB60@webaccess.indicator.be>
<1164638251.270 70.45.camel@localhost.localdomain>
Hi gnari,
I suppose your statement
test=# select '\x'||'65';
is done on some command line interface. I don't have that. I can only
use some client program. I'm using EMS SQL Manager 2007 and pgAdmin III
1.3
None of them accepts your statement.
My point is that in my first version of the function ( charset :=
charset || '\x65'; ) a unicode hex value for the letter e is stored in
charset.
When I try to do the same for a range of hex values ( FOR i IN
101..101 LOOP charset := charset || '\x' || to_hex(i); ) it is not
longer a bunch of hex values that get stored but a series of varchars.
When you run the first version of the function ( SELECT myfunction();
) 'e' is returned, with the second version 'x65' is returned, while I
want also 'e' to be returned.
Any ideas?
>>> Ragnar <gnari@hive.is> 2006-11-27 15:37 >>>
On mán, 2006-11-27 at 11:52 +0100, Bart Degryse wrote:
> Dear all,
> This works: SELECT '\x65'; => it returns the letter 'e'.
yes, but:
test=# select '\x'||'65';
?column?
----------
x65
(1 row)
> When I do the following in PL/PGSQL ....
> FOR i IN 101..101 LOOP
> charset := charset || '\x' || to_hex(i);
> END LOOP;
gnari
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: Bart.Degryse@indicator.be, gnari@hive.is
Subject: Re: UNICODE and PL/PGSQL
In-Reply-To: <456B0A47020000300000FC1E@webaccess.indicator.be>
* 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