| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Subject: | Re: nested hstore patch |
| Date: | 2013-11-19 16:04:25 |
| Message-ID: | 528B8C09.3020307@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/19/2013 11:00 AM, Robert Haas wrote:
> On Tue, Nov 19, 2013 at 10:55 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> On Tue, Nov 19, 2013 at 10:51:06AM -0500, Robert Haas wrote:
>>> I think this was the consensus solution when this was last discussed,
>>> and I support it. There is similar space for a binary XML data type
>>> if someone feels like implementing it. I think the names that were
>>> proposed previously were something like jsonb and xmlb.
>> The natural name is OBJSON, meaning object JSON, because as PostgreSQL
>> people, we have to double-use letters wherever possible. ;-)
> Personally, I think the patch author should just run ps auxww | md5 |
> sed 's/^[^0-9]//' | cut -c1-8 and call the new data type by the
> resulting name.
>
My personal vote goes for "marmaduke". I've been dying to call some
builtin object that for ages.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-11-19 16:07:53 | Re: Review: pre-commit triggers |
| Previous Message | Robert Haas | 2013-11-19 16:00:09 | Re: nested hstore patch |