| From: | "Sven R(dot) Kunze" <srkunze(at)mail(dot)de> |
|---|---|
| To: | Josh Berkus <josh(at)berkus(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Peter van Hardenberg <pvh(at)pvh(dot)ca> |
| Cc: | 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:10:42 |
| Message-ID: | 7b4e30d7-94a4-d8b8-3a78-8952dcbcf261@mail.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10.03.2017 20:28, Josh Berkus wrote:
> On 03/09/2017 10:12 AM, Sven R. Kunze wrote:
>>
>> SaltStack uses YAML for their tools, too. I personally can empathize
>> with them (as a user of configuration management) about this as writing
>> JSON would be nightmare with all the quoting, commas, curly braces etc.
>> But that's my own preference maybe.
> Yes, but automated tools can easily convert between JSON and
> newline-delimited YAML and back.
Sure. That wasn't point, though.
Sven
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2017-03-13 19:11:10 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |
| Previous Message | Heikki Linnakangas | 2017-03-13 19:07:39 | Re: Radix tree for character conversion |