| From: | "Sven R(dot) Kunze" <srkunze(at)mail(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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-09 18:24:37 |
| Message-ID: | d097d2d5-b290-e731-b0ee-9dbcf62a2e36@mail.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09.03.2017 18:58, Robert Haas wrote:
> Also, even if the superset thing were true on a theoretical plane, I'm
> not sure it would do us much good in practice. If we start using
> YAML-specific constructs, we won't have valid JSON any more. If we
> use only things that are legal in JSON, YAML's irrelevant.
That's true. I just wanted to share my view of the "date guessing" part
of pgpro's commits.
I don't have a good solution for it either, I can only tell that where I
work we do have same issues: either we guess by looking at the string
value or we know that "this particular key" must be a date.
Unsatisfied with either solution, we tend to use YAML for our APIs if
possible.
Regards,
Sven
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-03-09 18:26:50 | Re: Documentation improvements for partitioning |
| Previous Message | Robert Haas | 2017-03-09 18:14:20 | Re: foreign partition DDL regression tests |