Troels Arvin wrote:
On Fri, 15 Oct 2004 09:46:04 +, Andreas Pflug wrote:
When does it fail? Enable sql logging for that.
LOG: connection received: host=127.0.0.1 port=36036
LOG: connection authorized: user=troels database=template1
LOG: statement: SELECT oid, pg_encoding_to_char(encoding)
On Fri, 15 Oct 2004 09:46:04 +, Andreas Pflug wrote:
> When does it fail? Enable sql logging for that.
LOG: connection received: host=127.0.0.1 port=36036
LOG: connection authorized: user=troels database=template1
LOG: statement: SELECT oid, pg_encoding_to_char(encoding) AS encoding, datla
Troels Arvin wrote:
Hello,
I keep getting
ERROR: conversion between UNICODE and LATIN1 is not supported
when connecting from pgadmin3 beta 2 (checked out from CVS a little time
ago) to rather new checkout of PostgreSQL's CVS.
Is this a known problem/limitation?
No. When does it fail? Enable sql
Hello,
I keep getting
ERROR: conversion between UNICODE and LATIN1 is not supported
when connecting from pgadmin3 beta 2 (checked out from CVS a little time
ago) to rather new checkout of PostgreSQL's CVS.
Is this a known problem/limitation?
--
Greetings from Troels Arvin, Copenhagen, Denma