| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Benedikt Grundmann <bgrundmann(at)janestreet(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Farina <daniel(at)heroku(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json api WIP patch |
| Date: | 2013-02-04 18:07:31 |
| Message-ID: | 510FF8E3.1030203@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02/04/2013 12:57 PM, Merlin Moncure wrote:
> *) it's bad enough that we drift from sql naming conventions and all
> type manipulation functions (except in hstore) with type name.
> json_get etc. at least using operators allow avoiding some of that
> unnecessary verbosity. what's next: text_concatenate('foo', 'bar')?
>
This names aren't set in stone either. I've been expecting some
bikeshedding there, and I'm surprised there hasn't been more.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-02-04 19:38:01 | USE_PGXS contrib build is broken |
| Previous Message | Simon Riggs | 2013-02-04 18:06:51 | Re: proposal: ANSI SQL 2011 syntax for named parameters |