| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(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:32:54 |
| Message-ID: | 531840C6.3070608@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> In what sense are we really stopping hstore development if hstore2
> lives as jsonb? I have a hard time imagining someone dealing with the
> incompatibility that a user-facing hstore2 would introduce, while
> still preferring hstore syntax over json syntax given the choice.
> There are very rich facilities for manipulating json available in
> every programming language. The same is not true of hstore.
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.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-03-06 09:47:04 | Re: ALTER TABLE lock strength reduction patch is unsafe |
| Previous Message | Haribabu Kommi | 2014-03-06 09:17:20 | Re: contrib/cache_scan (Re: What's needed for cache-only table scan?) |