| From: | Maurice Aubrey <maurice(dot)aubrey(at)gmail(dot)com> |
|---|---|
| To: | Stuart McGraw <smcg4191(at)mtneva(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: jsonb_set() strictness considered harmful to data |
| Date: | 2019-10-24 02:18:45 |
| Message-ID: | CAMjjn=FcMdecBzzozUvSDq4iAUum4D=2Y5yNfhnMbuaty4FxTQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Wed, Oct 23, 2019 at 12:01 PM Stuart McGraw <smcg4191(at)mtneva(dot)com> wrote:
> When examples are given, they typically are with scalar values where
> such behavior makes sense: the resulting scalar value has to be NULL
> or non-NULL, it can't be both.
>
> It is less sensible with compound values where the rule can apply to
> individual scalar components. And indeed that is what Postgresql does
> for another compound type:
>
I agree completely. Scalar vs compound structure seems like the essential
difference.
You don't expect an operation on an element of a compound structure to be
able to effect the entire structure.
Maurice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2019-10-24 06:19:14 | Re: Composite type storage overhead |
| Previous Message | rob stone | 2019-10-24 01:52:36 | Re: jsonb_set() strictness considered harmful to data |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-10-24 02:42:04 | Re: v12.0: reindex CONCURRENTLY: lock ShareUpdateExclusiveLock on object 14185/39327/0 is already held |
| Previous Message | rob stone | 2019-10-24 01:52:36 | Re: jsonb_set() strictness considered harmful to data |