Return-Path: mao
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA13903; Tue, 22 Sep 92 19:25:56 -0700
Message-Id: <9209230225.AA13903@postgres.Berkeley.EDU>
From: <mao@postgres.berkeley.edu>
Subject: Re: <<<< UPDATING ARRAYS >>>>
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
In-Reply-To: Your message of Tue, 22 Sep 92 19:02:16 PST.
             <01GP4K0JCQWGAIBWIQ@otago.ac.nz> 
Date: Tue, 22 Sep 92 19:25:50 PDT

In message <01GP4K0JCQWGAIBWIQ@otago.ac.nz> you write:
> With regards to attributes of type array e.g text[100], is it possible once
> values have already been entered and saved to then update this list with extra
> elements.

no, what you propose doesn't work in version 4.0.  we hope to add this
sometime.

> One other question : Sets as attributes are not supported - would this not be
> a simple to define user type or are there hidden complexities involved?

there are semantic issues involved.  for example, you'd like to be able
to express, in the query language, a query that ran some function on each
of the values in a set.  that can't be supported without some extensions
to the postgres executor.  a graduate student here is looking into adding
support for sets as first-class objects in version 4.1.

					mike