Re: SQL/JSON in PostgreSQL

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Nico Williams <nico(at)cryptonector(dot)com>
Cc: "Sven R(dot) Kunze" <srkunze(at)mail(dot)de>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter van Hardenberg <pvh(at)pvh(dot)ca>, Andres Freund <andres(at)anarazel(dot)de>, Oleg Bartunov <obartunov(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, Teodor Sigaev <teodor(at)postgrespro(dot)ru>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: SQL/JSON in PostgreSQL
Date: 2017-03-13 06:31:51
Message-ID: CAFj8pRD7xS7bQCwh4jZgu3=sRL2Ai1CdcDER_QMCQe7E=zL0KQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2017-03-13 7:24 GMT+01:00 Nico Williams <nico(at)cryptonector(dot)com>:

> On Thu, Mar 09, 2017 at 07:12:07PM +0100, Sven R. Kunze wrote:
> > From my day-to-day work I can tell, the date(time) type is the only
> missing
> > piece of JSON to make it perfect for business applications (besides,
> maybe,
> > a "currency" type).
>
> And a binary type. And a chunked-string type (to avoid having to escape
> strings). And an interval type. And...
>

It is designed/born be simple - if you need some more complex, then you can
use XML with schema, ...

Pavel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-03-13 06:44:53 Re: Speedup twophase transactions
Previous Message Nico Williams 2017-03-13 06:24:39 Re: SQL/JSON in PostgreSQL