| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json api WIP patch |
| Date: | 2013-01-08 21:32:46 |
| Message-ID: | CAHyXU0wWHezyxAK_HBQX-R5BeEXAzr+R5sQ57z2vyQwDWijkKA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 8, 2013 at 3:19 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> On 1/7/13 5:15 PM, Andrew Dunstan wrote:
>> You (Merlin) have kindly volunteered to work on documentation, so before
>> we go too far with that any bikeshedding on names, or on the
>> functionality being provided, should now take place.
>
> Hmm, I was going to say, this patch contains no documentation, so I have
> no idea what it is supposed to do. "Recently discussed" isn't a good
> substitute for describing what the patch is supposed to accomplish.
Why not? There are functional examples in the docs and the purpose of
the various functions was hashed out pretty well a couple weeks back,
deficiencies corrected, etc.
reference: http://postgresql.1045698.n5.nabble.com/json-accessors-td5733929.html
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2013-01-08 21:38:52 | Re: PATCH: optimized DROP of multiple tables within a transaction |
| Previous Message | james | 2013-01-08 21:31:23 | Re: json api WIP patch |