| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: additional json functionality |
| Date: | 2013-11-15 21:12:16 |
| Message-ID: | 881C0CE9-8384-4292-9E92-03AB719F45AF@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Nov 15, 2013, at 12:37 PM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> It's making my head hurt, to be honest, and it sounds like a recipe for years and years of inconsistencies and bugs.
>
> I don't want to have two types, but I think I'd probably rather have two clean types than this. I can't imagine it being remotely acceptable to have behaviour depend in whether or not something was ever stored, which is what this looks like.
I disklike having two types (no, three -- there is hstore, too!). But if there is consensus for it (and I am not at all convinced that there is at this point), I can live with it. Docs would have to be pretty explicit, though.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2013-11-15 21:18:22 | Re: additional json functionality |
| Previous Message | Josh Berkus | 2013-11-15 21:11:46 | Re: Turning recovery.conf into GUCs |