Re: [HACKERS] SQL/JSON in PostgreSQL

Поиск
Список
Период
Сортировка
От Sven R. Kunze
Тема Re: [HACKERS] SQL/JSON in PostgreSQL
Дата
Msg-id 16a52989-e330-dcba-a82b-0306801cee42@mail.de
обсуждение исходный текст
Ответ на Re: [HACKERS] SQL/JSON in PostgreSQL  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: [HACKERS] SQL/JSON in PostgreSQL  (Magnus Hagander <magnus@hagander.net>)
Re: [HACKERS] SQL/JSON in PostgreSQL  (Josh Berkus <josh@berkus.org>)
Re: [HACKERS] SQL/JSON in PostgreSQL  (Nico Williams <nico@cryptonector.com>)
Список pgsql-hackers
On 08.03.2017 20:52, Magnus Hagander wrote:
On Wed, Mar 8, 2017 at 11:48 AM, Peter van Hardenberg <pvh@pvh.ca> wrote:
Small point of order: YAML is not strictly a super-set of JSON.

Editorializing slightly, I have not seen much interest in the world for YAML support though I'd be interested in evidence to the contrary.


The world of configuration management seems to for some reason run off YAML, but that's the only places I've seen it recently (ansible, puppet etc).

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.

(Btw. does "run off" mean like or avoid? At least my dictionaries tend to the latter.)

That said if we're introducing something new, it's usually better to copy from another format than to invite your own.

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).

Regards,
Sven

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] updating parallel.sgml
Следующее
От: Robert Haas
Дата:
Сообщение: Re: [HACKERS] foreign partition DDL regression tests