From: Bruce Momjian <maillist@candle.pha.pa.us>
Message-Id: <199908111414.KAA27351@candle.pha.pa.us>
Subject: Re: [HACKERS] libpgtcl and array fields return format - PROPOSAL
In-Reply-To: <37B17555.8FEDF23D@flex.ro> from Constantin Teodorescu at "Aug
 11,
	1999 01:06:29 pm"
To: Constantin Teodorescu <teo@flex.ro>
Date: Wed, 11 Aug 1999 10:14:09 -0400 (EDT)
CC: Thomas Lockhart <lockhart@alumni.caltech.edu>,
	PostgreSQL Interfaces <pgsql-interfaces@postgreSQL.org>,
	"pgsql-hackers@postgreSQL.org" <pgsql-hackers@postgreSQL.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> For the moment, the current syntax helps PgAccess. It returns exactly
> the same format as it would be used to INSERT INTO queries so if you
> would try to define a table with an array field of strings for example
> you are able to add records and update them directly from PgAccess.
> >From that point of view, the new array field return format would give me
> headaches for Pgaccess in order to restore the {"..","..",".."} format
> used for updating records.
> 
> Am I missing something about the *input* format?
> 
> On the other hand, I have discovered in the libpgtcl source that there
> is a TCL_ARRAYS that if defined, would return array fields format
> exactly as a tcl list. But it is not defined anywhere. I think that the
> behaviour of libpgtcl should be consistent so should we define
> TCL_ARRAYS by default in the next release?

That define is from Massimo.  Let's enable it.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026