| From: | Kaare Rasmussen <kaare(at)jasonic(dot)dk> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: json indexing and data types |
| Date: | 2015-12-03 04:48:06 |
| Message-ID: | 565FC986.1060502@jasonic.dk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2015-12-03 05:04, Tom Lane wrote:
> Yeah. The problem here is that a significant part of the argument for
> the JSON/JSONB datatypes was that they adhere to standards (RFC 7159
> in particular). I can't see us accepting a patch that changes them
> into JSON-plus-some-PG-enhancements.
Would be nice for my specific need, but probably wouldn't do a lot of
good in the long run.
> (Having said that, it sure looks to me like JSON's idea of a number is
> float/numeric, not merely int. Are you sure you need more capability
> in that department, and if so what exactly?)
Hmm, I think you're right, having just tried some conversions. But
still, I would have to rely on vodka (or similar) knowing this, I guess?
/kaare
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yelai, Ramkumar IN BLR STS | 2015-12-03 05:59:33 | Re: Pgbasebackup help |
| Previous Message | Kaare Rasmussen | 2015-12-03 04:43:14 | Re: json indexing and data types |