From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Jim Nasby <jim(at)nasby(dot)net> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Disallow arrays with non-standard lower bounds |
Date: | 2014-01-10 22:10:33 |
Message-ID: | CAMkU=1xsPanD5PbQwybcFmuWdYc=1F+xmFZokC2z5hbuXXOBPQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 10, 2014 at 1:26 PM, Jim Nasby <jim(at)nasby(dot)net> wrote:
> On 1/9/14, 10:58 PM, Tom Lane wrote:
>
>> Jim Nasby <jim(at)nasby(dot)net> writes:
>>
>>> ISTM that allowing users to pick arbitrary lower array bounds was a huge
>>> mistake. I've never seen anyone make use of it, can't think of any
>>> legitimate use cases for it, and hate the stupendous amount of extra code
>>> needed to deal with it.
>>>
>>
>> You lack imagination, sir.
>>
>
> Considering what you'd normally want to do in SQL, the only example I can
> think of is to not have the argument over 0 vs 1 based.
>
> Actually, I was thinking there might be some computational problems where
> changing lower bound would be nice, but then again, what other languages
> actually support this?
Perl does, though they regret it bitterly.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2014-01-10 22:14:47 | Re: Disallow arrays with non-standard lower bounds |
Previous Message | Kevin Grittner | 2014-01-10 22:10:16 | Re: Disallow arrays with non-standard lower bounds |