| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JSON for PG 9.2 |
| Date: | 2011-12-12 21:27:42 |
| Message-ID: | 4EE671CE.6010304@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/12/2011 03:54 PM, Robert Haas wrote:
> On Mon, Dec 12, 2011 at 3:38 PM, Simon Riggs<simon(at)2ndquadrant(dot)com> wrote:
>> Rather than fuss with specific data formats, why not implement
>> something a little more useful?
>>
>> At present we can have typmods passed as a cstring, so it should be
>> possible to add typmods onto the TEXT data type.
>>
>> e.g. TEXT('JSON'), TEXT('JSONB')
>>
[...]
> There are way too many places that assume that the typmod can
> just be discarded. I don't think that's going to fly, because
> =(text,text) probably has different semantics from =(json,json).
>
And certain places where they are not allowed at all, I think (unless I
am misremembering the early debates about enum types and output functions).
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2011-12-12 21:34:02 | Re: JSON for PG 9.2 |
| Previous Message | David E. Wheeler | 2011-12-12 21:26:00 | Re: JSON for PG 9.2 |