Re: Add json_typeof() and json_is_*() functions. - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Add json_typeof() and json_is_*() functions.
Date
Msg-id CAHyXU0wf4fPoZVKvSsMGsUQVP0Psu9FZqVYWT3tbtK2uq0w9Zw@mail.gmail.com
Whole thread Raw
In response to Re: Add json_typeof() and json_is_*() functions.  (Andrew Tipton <andrew@kiwidrew.com>)
Responses Re: Add json_typeof() and json_is_*() functions.  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Fri, Aug 2, 2013 at 7:22 AM, Andrew Tipton <andrew@kiwidrew.com> wrote:
> On Fri, Aug 2, 2013 at 8:12 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>>
>> +1, but I'm wondering why we need anything more than just
>> json_typeof().  Doesn't that pretty much cover it?
>
>
> I agree with Merlin that json_is_object() is superfluous, since it can just
> be replaced with json_typeof() = 'object'.  Likewise for json_is_array().
> But without json_is_scalar(), the choice is one of these two forms:
>   json_typeof() NOT IN ('object', 'array')
>   json_typeof() IN ('string', 'number', 'boolean', 'null')
>
> And it protects the user against forgetting about, say, the 'null' typeof()
> when constructing their check expression.

right: I was thinking also that if/when json were ever to get new
types, you'd appreciate that function.

merlin



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])
Next
From: Tom Lane
Date:
Subject: Re: Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review])