| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | 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 06:16:46 |
| Message-ID: | 531812CE.3010304@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/05/2014 09:07 PM, Peter Geoghegan wrote:
> It's hard to justify having a user-facing hstore2 on the grounds of
> backwards compatibility, and giving those stuck on hstore the benefit
> of all of these new capabilities. That's because we *cannot* really
> preserve compatibility, AFAICT. Many of the lines of the patch
> submitted are due to changes in the output format of hstore, and the
> need to update the hstore tests' expected results to reflect these
> changes. For example:
Thank you for checking that. Teodor's goal was that new-hstore be 100%
backwards-compatible with old-hstore. If we're breaking APIs, then it
doesn't really work to force users to upgrade the type, no?
Teodor, are these output changes things that can be made consistent, or
do we need separate hstore and hstore2 datatypes?
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2014-03-06 06:26:23 | Re: Fwd: patch: make_timestamp function |
| Previous Message | Peter Geoghegan | 2014-03-06 05:07:00 | Re: jsonb and nested hstore |