| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: additional json functionality |
| Date: | 2013-11-16 00:44:08 |
| Message-ID: | 5286BFD8.7040603@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/15/2013 07:32 PM, Josh Berkus wrote:
> On 11/15/2013 04:00 PM, David Johnston wrote:
>> Looking at this a different way: could we just implement BSON and leave json
>> alone?
>>
>> http://bsonspec.org/
> In short? No.
>
> For one thing, our storage format is different from theirs (better,
> frankly), and as a result is not compliant with their "standard".
>
> That's a reason why we won't use the name BSON, either, since it's a
> trademark of 10gen.
>
What is more, it has restrictions which we do not wish to have. See for
example its treatment of numerics.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-11-16 00:48:06 | Re: The number of character limitation of custom script on pgbench |
| Previous Message | Josh Berkus | 2013-11-16 00:32:30 | Re: additional json functionality |