From: | "Bart Degryse" <Bart(dot)Degryse(at)indicator(dot)be> |
---|---|
To: | <Markus Schaber <schabi(at)logix-tt(dot)com>, <pgsql-sql(at)postgresql(dot)org> |
Cc: | "Richard Huxton"<dev(at)archonet(dot)com> |
Subject: | Re: UNICODE and PL/PGSQL |
Date: | 2006-11-27 16:10:31 |
Message-ID: | 456B1C07020000300000FC7F@webaccess.indicator.be |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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 <schabi(at)logix-tt(dot)com> 2006-11-27 16:53 >>>
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: operator does not exist: character varying || bytea
> HINT: No operator matches the given name and argument type(s). You may
> need to add explicit type casts.
> CONTEXT: SQL statement "SELECT $1 || decode(to_hex( $2 ), 'hex')"
Hmm. Strange.
Does it happen in a plpgsql function, or when issuing the select as
PREPARE statement via pgadmin?
Which PostgreSQL version are you running?
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org
From | Date | Subject | |
---|---|---|---|
Next Message | Markus Schaber | 2006-11-27 16:34:16 | Re: UNICODE and PL/PGSQL |
Previous Message | Bart Degryse | 2006-11-27 16:05:19 | Re: UNICODE and PL/PGSQL |