Received: from flex.flex.ro (IDENT:root@[193.230.255.4])
	by hub.org (8.9.3/8.9.3) with ESMTP id CAA26181;
	Wed, 11 Aug 1999 02:20:13 -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 JAA32583;
	Wed, 11 Aug 1999 09:20:50 +0300
Sender: teo@flex.flex.ro
Message-ID: <37B1178F.1BDFB003@flex.ro>
Date: Wed, 11 Aug 1999 06:26:23 +0000
From: Constantin Teodorescu <teo@flex.ro>
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: PostgreSQL Interfaces <pgsql-interfaces@postgresql.org>,
	"pgsql-hackers@postgreSQL.org" <pgsql-hackers@postgresql.org>
Subject: libpgtcl and array fields return format - PROPOSAL
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi,

In libpgtcl, pg_select an array field is return as the following string:

{"red","blue","green"}

and it's rather difficult to process them as a normal tcl list.
The same thing for pg_exec, pg_result/tupleArray

I think it would be better to return the string as:

"red" "blue" "green"

and tcl users could directly process the array as an ordinary tcl list.

As far as I know, arrays are not heavily used by libpgtcl users (thought
it's an interesting feature) so changing format would not affect too
many applications but will encourage array field usage in future.

What do you think?

Constantin Teodorescu
FLEX Consulting Braila, ROMANIA