Re: Cast jsonb to numeric, int, float, bool - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Cast jsonb to numeric, int, float, bool
Date
Msg-id CA+Tgmob08StTV9yu04D0idRFNMh+UoyKax5Otvrix7rEZC8rMw@mail.gmail.com
Whole thread Raw
In response to Re: Cast jsonb to numeric, int, float, bool  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: Cast jsonb to numeric, int, float, bool  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
Re: Cast jsonb to numeric, int, float, bool  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
On Thu, Mar 29, 2018 at 9:35 AM, Teodor Sigaev <teodor@sigaev.ru> wrote:
> Thanks for everyone, pushed with some editorization

I would like to complain about this patch.  First, I think that it
would've been a better idea to use functions for this rather than
operators, because now ::text does something totally unlike what ::int
does, and that's confusing.  If we had json_to_WHATEVER for various
values of WHATEVER then all of the conversions could be spelled
similarly; as the commit message right points out, the cast can only
do one thing.

Also, I think the error messages aren't great:

+select '[]'::jsonb::bool;
+ERROR:  jsonb value must be boolean

In this simple scenario, it's clear enough what has gone wrong, but in
a more complicated case I suspect people will have a hard time
figuring out what the source of that error message is.  It seems like
it would be better to say something about casting or converting in the
error message, to give users a clue.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: pgsql: Add documentation for the JIT feature.
Next
From: Peter Geoghegan
Date:
Subject: Re: pgsql: Add documentation for the JIT feature.