Due to a lack of time, I'm closing the thread. It takes a little more
code, but I've decided to just forget about the loop and write every
single statement in my function.
Thanks anyway for explaning and brainstorming.
>>> Ragnar <[EMAIL PROTECTED]> 2006-11-28 10:28 >>>
On þri, 2006-11-28 at 09:14
On þri, 2006-11-28 at 09:14 +0100, Bart Degryse wrote:
> Yes, I tried and it didn't work. PostgreSQL surely makes something of
> it, but not the right characters.
maybe you should show us exacly what you did, and what
you got, and what you expected
> Unless Markus can make his idea using "decode"
Basically, I agree with your viewpoint on developer's permissions, but any
annoyance can be fixed with a large enough paycheck...
>>> Markus Schaber <[EMAIL PROTECTED]> 2006-11-27 17:34 >>>
Hi, Bart,
Bart Degryse wrote:
> I haven't got enough permissions to install new programs. Big brother...
Yes, I tried and it didn't work. PostgreSQL surely makes something of it, but
not the right characters.
Unless Markus can make his idea using "decode" work, this might be something
pl/pgsql cannot do.
>>> Richard Huxton 2006-11-27 17:34 >>>
Bart Degryse wrote:
> As the manual says : Character w
Hi, Bart,
Bart Degryse wrote:
> I haven't got enough permissions to install new programs. Big brother... ;-)
A developer doesn't get the permissions to use the tools he need for his
work?
Developers absolutely _must_ have root / admin permissions on their own
workstations, that's a prerequiremen
Bart Degryse wrote:
As the manual says : Character with the given ASCII code
I need characters outside the ASCII range. Something like
charset := charset || '\xC2\x' || to_hex(i)';
Well, if you've tried it for characters > 127 and it didn't work then I
don't know that it is possible at all.
I haven't got enough permissions to install new programs. Big brother... ;-)
I get the error in a plpgsql function
I use PostgreSQL 8.1.4 with EMS SQL Manager 2005 (3.6.0.1).
>>> Markus Schaber <[EMAIL PROTECTED]> 2006-11-27 16:53 >>>
Hi, Bart,
Bart Degryse wrote:
> I should have said "The ICT
As the manual says : Character with the given ASCII code
I need characters outside the ASCII range. Something like
charset := charset || '\xC2\x' || to_hex(i)';
>>> Richard Huxton 2006-11-27 16:53 >>>
Bart Degryse wrote:
> Hi Markus,
> I should have said "The ICT department doesn't give me acc
This is an automated response.
Your email...
From:[EMAIL PROTECTED]
Subject: Re: [SQL] UNICODE and PL/PGSQL
has been successfully received and I will reply as soon as possible.
Thank you.
---(end of broadcast)---
TIP 9: In versions below
Hi, Bart,
Bart Degryse wrote:
> I should have said "The ICT department doesn't give me access to the
> psql command line interface".
Hmm, and you can't install psql on the same host you use to run pgadmin?
It's just a client, that connects to PostgreSQL the same way as pgamdin.
> ERROR: oper
Bart Degryse wrote:
Hi Markus,
I should have said "The ICT department doesn't give me access to the psql command
line interface".
Thanks for explaining what goes wrong. I now understand the problem. It doesn't
solve it though.
What's wrong with the chr() function?
http://www.postgresql.org/do
On mán, 2006-11-27 at 15:54 +0100, Bart Degryse wrote:
> 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 yo
Hi Markus,
I should have said "The ICT department doesn't give me access to the psql
command line interface".
Thanks for explaining what goes wrong. I now understand the problem. It doesn't
solve it though.
I haven't tried your first suggestion since ASCII won't be good enough. I also
need to be
This is an automated response.
Your email...
From:[EMAIL PROTECTED]
Subject: Re: [SQL] UNICODE and PL/PGSQL
has been successfully received and I will reply as soon as possible.
Thank you.
---(end of broadcast)---
TIP 4: Have you searched
Hi, Bart,
Bart Degryse wrote:
> 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.
All versions of PostgreSQL I know are shipped with "psql" as command
line interface. (It's a client program, act
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 (
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 || '
Dear all,
This works: SELECT '\x65'; => it returns the letter 'e'.
When I do the following in PL/PGSQL it returns the same letter 'e' (as might be
expected);
CREATE OR REPLACE FUNCTION "public"."myfunction" (out result varchar) RETURNS
varchar AS
$body$
DECLARE
charset varchar := '';
BEGIN
18 matches
Mail list logo
