News for hackers. Stuff that matters.

A comment on Postgres 15 improves UNIQUE and NULL. Parent comment

Re:Postgres 15 improves UNIQUE and NULL by tinco on Monday July 11, 2022 @07:00AM (#32054521)
Not parent, and not necessarily agree, but one should throw a parser/typecheck error and the other should not.
[ Parent | on HN ]
Re:Postgres 15 improves UNIQUE and NULL by CipherThrowaway on Monday July 11, 2022 @07:13AM (#32054598)
In cases where the field is required I would agree. But in the context of an update request, {"foo":null} and {} might both be valid with different semantics. "Update this field to null" vs "don't update this field"
[ Parent | on HN ]
Re:Postgres 15 improves UNIQUE and NULL by dbrgn on Monday July 11, 2022 @07:23AM (#32054665)
A similar issue is {}, {"mylist": null} and {"mylist": []}. Three ways to represent a missing or empty list.
[ Parent | on HN ]