Re: pltcl bug in 7.2?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Yury Don <yura(at)vpcit(dot)ru>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pltcl bug in 7.2?
Date: 2002-04-19 14:32:16
Message-ID: 27903.1019226736@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yury Don <yura(at)vpcit(dot)ru> writes:
> Hello All,
> We have a database with koi8-r encoding, tables and fields names
> mostly in russian, and we have a trigger function on pltcl. With postgresql 7.1 everything
> worked well, but in 7.2 we are getting an error "utf_to_local: could
> not convert UTF-8" in the following construction
> foreach field [array names NEW] {
> if {[info exists OLD(${field})]} ....

Hmm. Someone added code in 7.2 to support conversion between the
database's encoding (whatever you specified with -E) and the UTF-8
encoding that Tcl wants to use all the time. Sounds like you've
found a bug in that code.

> Also this error occures in any calling of NEW or OLD, for example
> [array get NEW] also raises those error.

Do you see it *only* in references to NEW/OLD? Can you pass the
same data in normal parameters to a Tcl function?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Darren Ferguson 2002-04-19 15:09:11 Re: pltcl bug in 7.2?
Previous Message Jean-Michel POURE 2002-04-19 12:52:29 Re: Insert Unicode