Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?

2022-06-18 Thread Bryn Llewellyn
> haram...@gmail.com wrote > >> b...@yugabyte.com wrote: >> >> I implemented two complementary functions: >> >> —"no_null_keys()" checks that a "jsonb" value has no occurrences of « "some >> key": null » >> >> —"strip_null_keys()" removes « "some key": null » occurrences from a "jsonb" >> val

Re: ISBN (was: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?)

2022-06-18 Thread Bryn Llewellyn
> hjp-pg...@hjp.at wrote: > >> Bryn wrote: >> >> "isbn" — string >> values must be unique across the entire set of documents (in other words, it >> defines the unique business key); values must have this pattern: >> >> « ^[0-9]{3}-[0-9]{1}-[0-9]{2}-[0-9]{6}-[0-9]{1}$ » > > Completely off-topic

Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?

2022-06-18 Thread Alban Hertroys
> On 18 Jun 2022, at 2:14, Bryn Llewellyn wrote: > > I implemented two complementary functions: > > —"no_null_keys()" checks that a "jsonb" value has no occurrences of « "some > key": null » > > —"strip_null_keys()" removes « "some key": null » occurrences from a "jsonb" > value > > The co

Re:

2022-06-18 Thread Peter J. Holzer
On 2022-06-17 10:38:57 +0800, Abdul Qoyyuum wrote: > Best if you just maintain the logs into a log file instead of a database > table.  That depends on what you want to use those logs for. If you just want to look at them when something goes wrong, I agree: Logs files are simple, fast to write, t