Re: Array behavior oddities

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Array behavior oddities
Date: 2008-01-15 04:50:22
Message-ID: 13177.1200372622@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> If any dimension is written as a slice, i.e. contains a colon, then all
> dimensions are treated as slices.

> Is the the behavior of assuming an entry with no colon is a slice what
> we want, or are we just stuck with it?

Why do you find that surprising? It's either a slice or it isn't,
there's no halfway point. Are you proposing to throw an error if only
some of the subscripts have colons? What would be the point?

> Is there a reason out-of-bounds array accesses behave differently for
> slices and non-slices?

History (although "sloppy original implementation" would do too). I'm
not sure if we should try to clean it up --- there've not been that many
complaints, but I'm sure we'd get complaints from people whose code
stopped working, if we change it.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Markus Schiltknecht 2008-01-15 08:42:56 Re: Declarative partitioning grammar
Previous Message Tom Lane 2008-01-15 04:35:30 Re: SSL over Unix-domain sockets