Skip site navigation (1) Skip section navigation (2)

Re: libpgtcl and encoding

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sandro Dentella <sandro(dot)dentella(at)tin(dot)it>
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: libpgtcl and encoding
Date: 2002-06-11 17:44:46
Message-ID: 2554.1023817486@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-interfaces
Sandro Dentella <sandro(dot)dentella(at)tin(dot)it> writes:
> This is the output on the machine where tha database that I *cannot* connect
> to (if the encoding is SQL_ASCII, no problem if UNICODE)
> --with-tcl --bindir /usr/bin/ --with-tclconfig=/opt/tcltk/lib --without-tk

Well, there's your problem: no multibyte support at all on the server.
Recent releases of libpgtcl can only talk to multibyte-enabled servers
because of Tcl's decision to be internally Unicode-only.  You'll need
both --enable-multibyte and --enable-unicode-conversion at the server.

			regards, tom lane

In response to

pgsql-interfaces by date

Next:From: Amit LambaDate: 2002-06-11 18:31:14
Subject: unable to create postgresql.jar
Previous:From: Sandro DentellaDate: 2002-06-11 17:23:33
Subject: Re: libpgtcl and encoding

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group