| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JSON Function Bike Shedding |
| Date: | 2013-02-16 19:55:26 |
| Message-ID: | 4DBA33CD-9485-4503-B32C-8E42DEB58827@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Feb 16, 2013, at 8:57 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> I have had a look at doing something like this with the json_get functions. The trouble is that the best way to do it is to have json_get take "variadic any", but then string literals come in as unknown rather than as text, which makes things fairly ugly. If we force people to cast path elements to text then I think the cure is worse than the disease. I think the best we can do here is possibly to provide json_get and json_get_text taking either a single int or variadic text[], and json_get_path and json_get_path_text taking non-variadic text[].
Why not also one taking a single text?
get(text)
get(int)
get(variadic text[])
?
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-02-16 20:05:28 | Re: JSON Function Bike Shedding |
| Previous Message | Noah Misch | 2013-02-16 19:46:45 | Re: Materialized views WIP patch |