| From: | "Sven R(dot) Kunze" <srkunze(at)mail(dot)de> |
|---|---|
| To: | Nico Williams <nico(at)cryptonector(dot)com> |
| Cc: | 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>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, 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 19:22:04 |
| Message-ID: | 3c4e1000-0697-eee8-78ae-2f6ba0f7ef96@mail.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 13.03.2017 07:24, Nico Williams wrote:
> 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...
YMMV but I tend to say that those aren't the usual types of a business
application where I come from.
Answering questions like "how many" (integer), "what" (text) and "when"
(date) is far more common than "give me that binary blob" at least in
the domain where I work. Never had the necessity for an interval type;
usually had a start and end value where the "interval" was derived from
those values.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-03-13 19:24:30 | Re: Partition-wise join for join between (declaratively) partitioned tables |
| Previous Message | Daniel Verite | 2017-03-13 19:11:10 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |