Re: "select ('{}'::text[])[1]" returns NULL -- is it correct?

From: "Nikolay Samokhvalov" <nikolay(at)samokhvalov(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: "select ('{}'::text[])[1]" returns NULL -- is it correct?
Date: 2007-04-10 14:25:16
Message-ID: e431ff4c0704100725v7238cd1w840b3d32bf965f31@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 4/10/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Nikolay Samokhvalov" <nikolay(at)samokhvalov(dot)com> writes:
> > I remember several cases when people (e.g. me :-) ) were spending some
> > time trying to find an error in some pl/pgsql function and the reason
> > lied in incorrect work with arrays (i.e. messages like "index is out
> > of bounds" and "index cannot be negative number" would help, surely).
>
> Well, if indexes *couldn't* be negative numbers then that might be
> helpful, but they can.
>

Ooops :-) OK, my proposal is narrowing to very simple one: what about
triggering WARNINGs when user tries to access nonexistent element of
array?

--
Best regards,
Nikolay

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Luke Lonergan 2007-04-10 14:30:38 Re: TOASTing smaller things
Previous Message Tom Lane 2007-04-10 14:23:42 Re: Anyone interested in improving postgresql scaling?