| From: | Brendan Jurd <direvus(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Florian Pflug <fgp(at)phlo(dot)org>, Josh Berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL) |
| Date: | 2013-04-05 01:51:56 |
| Message-ID: | CADxJZo14Gjn=EeBE9TCVEwAUbmpYDyL5yD9s3R5vk_EWtVpmvg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5 April 2013 07:43, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Well, if we're going to take that hard a line on it, then we can't
> change anything about array data storage or the existing functions'
> behavior; which leaves us with either doing nothing at all, or
> inventing new functions that have saner behavior while leaving the
> old ones in place.
And then we are in the awkward position of trying to explain the
differences in behaviour between the old and new functions ...
presumably with a dash of "for historical reasons" and a sprinkling of
"to preserve compatibility" in every other paragraph.
The other suggestion that had been tossed around elsewhere upthread
was inventing a new type that serves the demand for a straightforward
mutable list, which has exactly one dimension, and which may be
sensibly empty. Those few who are interested in dimensions >= 2 could
keep on using "arrays", with all their backwards-compatible silliness
intact, and everybody else could migrate to "lists" at their leisure.
I don't hate the latter idea from a user perspective, but from a
developer perspective I suspect there are valid objections to be made.
Cheers,
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2013-04-05 01:59:40 | Re: corrupt pages detected by enabling checksums |
| Previous Message | Tom Lane | 2013-04-05 01:06:15 | Re: corrupt pages detected by enabling checksums |