Return-Path: aoki
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA21072; Wed, 17 Mar 93 11:00:38 -0800
Message-Id: <9303171900.AA21072@postgres.Berkeley.EDU>
From: aoki@postgres.berkeley.edu (Paul M. Aoki)
Subject: Re: variable length arrays
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
In-Reply-To: Your message of Wed, 17 Mar 93 07:19:31 -0800 
	     <9303171519.AA02265@sherlock.Berkeley.EDU> 
Date: Wed, 17 Mar 93 11:00:51 -0800
Sender: aoki@postgres.Berkeley.EDU
X-Mts: smtp

ray@sherlock.Berkeley.EDU (Ray R. Larson) writes:
> {1,2} was OK and made sense {1} made sense but wasn't OK -- and I had a
> multi-megabyte file to load of some thousands of these that I didn't want 
> to edit by hand. Anyhow, everyone should probably ignore my cheap hack
> and quote all your array elements.

It's no more a cheap hack than the current fix (which is admittedly
pretty arbitrary...).  I was just explaining what the current stuff does 
and why.  I'm sure many people will *want* your semantics, in which case 
they can apply your patch.  It's probably better to accept {1} than to 
care about { } but since {1} was *already* broken and { } wasn't, I didn't
want to confuse people even more :-)

Sunita Sarawagi is highly and personally offended by the lack of 
multidimensional arrays and is rewriting the array code anyway ...
stay tuned :-)
