Re: SQL/JSON revisited (documentation) - Mailing list pgsql-hackers

From Erik Rijkers
Subject Re: SQL/JSON revisited (documentation)
Date
Msg-id 185ff744-c00f-a852-9c00-8e39b35b613c@xs4all.nl
Whole thread Raw
In response to Re: SQL/JSON revisited  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
Hi,

IS JSON is documented as:

expression IS [ NOT ] JSON
   [ { VALUE | SCALAR | ARRAY | OBJECT } ]
   [ { WITH | WITHOUT } UNIQUE [ KEYS ] ]

which is fine but 'VALUE' is nowhere mentioned
(except in the commit-message as: IS JSON [VALUE] )

Unless I'm mistaken 'VALUE' does indeed not change an IS JSON statement, 
so to document we could simply insert this line (as in the attached):

"The VALUE key word is optional noise."

Somewhere in its text in func.sgml, which is now:

"This predicate tests whether expression can be parsed as JSON, possibly 
of a specified type.  If SCALAR or ARRAY or OBJECT is specified, the 
test is whether or not the JSON is of that particular type. If WITH 
UNIQUE KEYS is specified, then any object in the expression is also 
tested to see if it has duplicate keys."


Erik Rijkers

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Various typo fixes
Next
From: Michael Paquier
Date:
Subject: Re: Add index scan progress to pg_stat_progress_vacuum