From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hannu Krosing <hannu(at)tm(dot)ee>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SQL99 ARRAY support proposal |
Date: | 2003-03-13 01:23:09 |
Message-ID: | Pine.LNX.4.44.0303122311400.1643-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Joe Conway writes:
> 2) Implement the following new builtin functions
> array_push(anyarray, anyelement) returns anyarray
> array_pop(anyarray) returns anyelement
> array_subscript(anyarray, int) yields anyelement
> singleton_array(anyelement) returns anyarray
> - any reason not to call this one simply "array"?
> split(text, text) returns text[]
> - split string into array on delimiter
> implode(text[], text) returns text
> - join array elements into a string using given string delimiter
I think this goes too far. It is just an invitation to people to create
bad database designs by using arrays as lists. Create an array support
package on gborg if you like, but I feel this should not be in the
mainline.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2003-03-13 01:30:07 | Re: regproc's lack of certainty is dangerous |
Previous Message | Tom Lane | 2003-03-12 23:03:56 | Re: regproc's lack of certainty is dangerous |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2003-03-13 04:01:57 | Re: SQL99 ARRAY support proposal |
Previous Message | Neil Conway | 2003-03-12 21:52:38 | minor SELECT doc patch |