| From: | Nikhil Ingale <niks(dot)bgm(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: IS JSON STRICT - In oracle => postgres ?? |
| Date: | 2023-06-20 08:57:20 |
| Message-ID: | CALXkTpyq1J+QpYJ7xuoS8+sVpAFy2De2QKak6h1ELYvcqgc7Sw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Information from you guys helped to resolve the issue.
Thank you all for the valuable inputs.
On Tue, Jun 20, 2023 at 1:37 PM Peter Eisentraut <peter(at)eisentraut(dot)org>
wrote:
> On 14.06.23 12:00, Nikhil Ingale wrote:
> > In oracle we can use the *is json* check constraint for the json column
> > to ensure the data is well formed.
> >
> > How do we ensure the same in postgres database?
>
> PostgreSQL 16 has an IS JSON predicate.
>
> It doesn't have a STRICT clause, which I don't see in the SQL standard.
> So it might not do exactly the same thing.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2023-06-20 10:49:04 | Re: What does invalid_transaction_state 25000 mean |
| Previous Message | Peter Eisentraut | 2023-06-20 08:07:05 | Re: IS JSON STRICT - In oracle => postgres ?? |