On 20 March 2015 at 14:58, Tom Lane wrote:
> AFAICS, array_remove keeps the existing lower bound number.
>
Thank you for explanation. This is not specified in
http://www.postgresql.org/docs/current/static/functions-array.html#ARRAY-FUNCTIONS-TABLE
so I was not sure.
Regards,
Matija Lesar
Matija Lesar writes:
> should not in example below array_remove return same results?
AFAICS, array_remove keeps the existing lower bound number. I don't
see anything particularly wrong with that definition.
Even if we didn't care about backwards compatibility, it would require
nontrivial effort
Hi,
should not in example below array_remove return same results?
test1=# create temp table tmptest (trid text[]);
CREATE TABLE
test1=# insert into tmptest values(null::text[]);
INSERT 0 1
test1=# update tmptest set trid[2:4]='{b,NULL,d}';
UPDATE 1
test1=# select trid,array_remove(trid,
NULL::tex
