Received: from flex.flex.ro (IDENT:root@[193.230.255.4]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA11072 for ; Wed, 11 Aug 1999 10:55:18 -0400 (EDT) (envelope-from teo@flex.ro) Received: from flex.ro (IDENT:teo@teo.flex.ro [193.230.255.3]) by flex.flex.ro (8.9.3/8.9.3) with ESMTP id RAA14722; Wed, 11 Aug 1999 17:55:48 +0300 Sender: teo@flex.flex.ro Message-ID: <37B19041.2FBAA5AE@flex.ro> Date: Wed, 11 Aug 1999 15:01:21 +0000 From: Constantin Teodorescu Organization: FLEX Consulting Braila X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.9 i586) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane CC: PostgreSQL Interfaces Subject: Re: [INTERFACES] libpgtcl and array fields return format - PROPOSAL References: <7653.934382778@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Tom Lane wrote: > > As you noticed later, there is some optional TCL_ARRAYS code that > purports to do something like this, but I think it's pretty broken. > > What seems like it would be fairly safe is to introduce separate Tcl > functions that convert between Postgres array format and Tcl list > format, and leave it to the user to apply these functions to data that > he knows is arrays... This is a better idea. I have recompiled libpgtcl with TCL_ARRAYS and noticed that you can fool it by sending a string field formatted as an array and he makes the translation into the list. Not good :-( -- Constantin Teodorescu FLEX Consulting Braila, ROMANIA