Re: [BUGS] BUG #14903: problem with bool array

From: Mike Porter <mike(at)udel(dot)edu>
To: arclight1995(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #14903: problem with bool array
Date: 2017-11-13 14:44:33
Message-ID: nycvar.BFK.7.76.1711130944120.12067@qbp.ybpny
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, 13 Nov 2017, arclight1995(at)gmail(dot)com wrote:

"The array subscript numbers are written within square brackets. By
default PostgreSQL uses a one-based numbering convention for arrays,
that is, an array of n elements starts with array[1] and ends with
array[n]."

> The following bug has been logged on the website:
>
> Bug reference: 14903
> Logged by: Roman Morozov
> Email address: arclight1995(at)gmail(dot)com
> PostgreSQL version: 9.6.5
> Operating system: PostgreSQL 9.6.5 on x86_64-pc-linux-gnu, compiled
> Description:
>
> 1) set value for field with type bool array:
> update "ContractorImage"
> set "States" =
> '{f,f,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL}'
> 2) try to change first value of array:
> update "ContractorImage" set "States"[0] = true
>
> 3) instead of '{t,f,null,...}' it becomes '{t,f,f,null,...}'. why doesd
> first element have index 1 instead of 0 ?
>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

-
Mike Porter
PGP Fingerprint: 139B 5431 9346 A577 C0F8 6C76 635D 6C9D 5ABB D433
Old Key: F4 AE E1 9F 67 F7 DA EA 2F D2 37 F3 99 ED D1 C2

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-11-13 15:23:23 Re: [BUGS] BUG #14902: valgrind - problem in PQconnectdb - pqSaveParameterStatus reported
Previous Message David Rowley 2017-11-13 13:35:24 Re: [BUGS] BUG #14899: not null constraint cann't improve the planner