From: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Erik Wienhold <ewie(at)ewie(dot)name>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: missing something about json syntax |
Date: | 2023-04-21 10:22:52 |
Message-ID: | CADX_1abh6EevZ4hnoSyDJcKjL4OgOfmJMNQqkw3StgOn14XUHg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Ok, thanks.
Le jeu. 20 avr. 2023 à 22:42, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> a écrit :
> Marc Millas <marc(dot)millas(at)mokadb(dot)com> writes:
> > but it doesnt explain how postgres is able to put a scalar in a json or
> > jsonb column without pb:
> > I don't understand how this ('"{\"t\"}"') can be considered a valid
> enough
> > json to be inserted in a json column
> > and at the same time invalid for all other json uses.
>
> That's a bare string (it's not an object). That's valid JSON per
> RFC 7159:
>
> JSON can represent four primitive types (strings, numbers, booleans,
> and null) and two structured types (objects and arrays).
> ...
> A JSON text is a serialized value. Note that certain previous
> specifications of JSON constrained a JSON text to be an object or an
> array.
>
> However, there certainly are some operations that require the top-level
> value to be an object or array.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Wu | 2023-04-21 14:06:41 | HOT update: why must ALL indexes should be update? |
Previous Message | Amit Kapila | 2023-04-21 09:16:51 | Re: Support logical replication of DDLs |