| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: json docs fixup |
| Date: | 2013-09-17 14:21:42 |
| Message-ID: | CA+TgmoaKGzuc5ab5nVEV_q7XwBQP1a6J-XkvAOjMqCS1c-uncg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Sep 14, 2013 at 3:23 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> While writing slides for pgopen next week, I noticed that the JSON docs on
> json_populate_record and json_populate_recordset contain this sentence:
>
> A column may only be specified once.
>
>
> IIRC we removed that restriction during development, so unless there is a
> squawk I am going to simply remove that sentence where it occurs. Or should
> we say something like:
>
> If a column is specified more than once, the last value is used.
If the latter statement is accurate, I favor including it, versus
saying nothing on the topic.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-09-17 14:23:30 | Re: [RFC] Extend namespace of valid guc names |
| Previous Message | Robert Haas | 2013-09-17 14:15:47 | Re: unaccent module - two params function should be immutable |