Re: libpgtcl and encoding

On Tue, Jun 11, 2002 at 12:48:08PM -0400, Tom Lane wrote:
> Sandro Dentella <sandro(dot)dentella(at)tin(dot)it> writes:
> > On Sun, Jun 09, 2002 at 11:43:22AM -0400, Tom Lane wrote:
> >> Was the 7.1 installation built with --enable-unicode-conversion ?
>
> > I francly don't remember. Is there a way to understand it from the binaries?
>
> pg_config --configure

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

This is the output on the machine (debian woody) where libpgtcl is:

--with-template=linux --prefix=/usr/lib/postgresql
--enable-unicode-conversion
--with-includes=/usr/include/tcl8.3 --includedir=/usr/include/postgresql
--with-python --with-openssl --with-gnu-ld --disable-rpath --enable-odbc
--with-unixodbc --with-CXX --enable-recode --with-tcl --with-perl
--with-pam --enable-multibyte --enable-debug --enable-syslog
--enable-locale --with-tclconfig=/usr/lib/tcl8.3
--with-tkconfig=/usr/lib/tk8.3 --with-maxbackends=64 --with-pgport=5432

> > and again: is there a way to start a connection w/ libpgtcl forcing a
> > particular encoding like wuold be w/ PGCLIENTENCODING environment variable?
>
> libpgtcl uses libpq, so it should respond to PGCLIENTENCODING.

Should... here is what happens:

[sandro(at)bluff] sandro $ export PGCLIENTENCODING=SQL_ASCII
[sandro(at)bluff] sandro $ tclsh
% load libpgtcl.so
% set p [pg_connect -conninfo "host=my_host dbname=danze \
user=sandro password=xxx"]

Connection to database failed
ERROR: Conversion between UNICODE and SQL_ASCII is not supported

regards

sandro
*:-)

--
Sandro Dentella *:-)
e-mail: sandro(dot)dentella(at)tin(dot)it
http://www.tksql.org TkSQL Home page - My GPL work