Thomas Lockhart wrote:
>
> > > > 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.
>
> Would it be also possible to use simple lists for arrays on *input* as
> well as output? The implementation would be symmetric and (presumably)
> easier to use...
I am note sure that I am understanding the problem.
There is no *input* format in Tcl.
The only way for adding data to a table is:
pg_exec $dbc "insert into ....." and that's the PostgreSQL syntax.
There's no "living" snapshots in Tcl as in JDBC 2 (updatable
recordsets).
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?
--
Constantin Teodorescu
FLEX Consulting Braila, ROMANIA
