Re: jsonb and nested hstore

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>, david(at)justatheory(dot)com
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Christophe Pettus <xof(at)thebuild(dot)com>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb and nested hstore
Date: 2014-03-06 09:51:54
Message-ID: CAM3SWZTtZZqmAb1oXWXzSFYnOw26OsBJwaqP7ZqKpEzCyaRv9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 6, 2014 at 1:32 AM, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
> It's true for perl. Syntax of hstore is close to hash/array syntax and it's
> easy serialize/deserialize hstore to/from perl. Syntax of hstore was
> inspired by perl.

I understand that. There is a module on CPAN called Pg::hstore that
will do this; it appears to have been around since 2011. I don't use
Perl, so I don't know a lot about it. Perhaps David Wheeler has an
opinion on the value of Perl-like syntax, as a long time Perl
enthusiast?

In any case, Perl has excellent support for JSON, just like every
other language - you are at no particular advantage in Perl by having
a format that happens to more closely resemble the format of Perl
hashes and arrays. I really feel that we should concentrate our
efforts on one standardized format here. It makes the effort to
integrate your good work, in a way that makes it available to everyone
so much easier.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kohei KaiGai 2014-03-06 11:15:59 Re: contrib/cache_scan (Re: What's needed for cache-only table scan?)
Previous Message Simon Riggs 2014-03-06 09:47:04 Re: ALTER TABLE lock strength reduction patch is unsafe