Re: libpgtcl doesn't use UTF encoding of TCL - Mailing list pgsql-bugs

From Tom Lane
Subject Re: libpgtcl doesn't use UTF encoding of TCL
Date
Msg-id 9073.995482402@sss.pgh.pa.us
Whole thread Raw
In response to Re: libpgtcl doesn't use UTF encoding of TCL  (Reinhard Max <max@suse.de>)
Responses Re: libpgtcl doesn't use UTF encoding of TCL  (Reinhard Max <max@suse.de>)
Re: libpgtcl doesn't use UTF encoding of TCL  (Reinhard Max <max@suse.de>)
Re: libpgtcl doesn't use UTF encoding of TCL  (Eugene Fokin <elf@solvo.ru>)
List pgsql-bugs
Reinhard Max <max@suse.de> writes:
> On Wed, 18 Jul 2001, Bruce Momjian wrote:
>> Do you have any idea how this will work with earlier TCL versions?

> It won't. If pgtcl is supposed to still be able to compile with older
> versions of Tcl, the changes have to be made a compile time option.

Please do that and resubmit the patch.  We really don't want to give up
backwards compatibility just yet.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Reinhard Max
Date:
Subject: Re: libpgtcl doesn't use UTF encoding of TCL
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Two foreign keys in one table both referencing same record in primary table gives error on update of primary table