BUG #14213: bug in hstore_to_json_loose() function

Started by Nonamealmost 10 years ago3 messagesbugs
Jump to latest
#1Noname
knut@wehrle.org

The following bug has been logged on the website:

Bug reference: 14213
Logged by: Knut Wehrle
Email address: knut@wehrle.org
PostgreSQL version: 9.4.5
Operating system: Window 7 Pro SP1
Description:

I get an arrow with the following command:

select hstore_to_json_loose(hstore('"date"=>"2016-06-24"'))->>'date'

The problem is, that the function is not generating an ISO date string but a
mathematical formula: 2016 - 06 - 24 = 1986!

Probably this is the intended way to handle this kind of data, but then the
'->>' operator would be buggy.

regards knut

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Noname (#1)
Re: BUG #14213: bug in hstore_to_json_loose() function

knut@wehrle.org writes:

PostgreSQL version: 9.4.5

I get an arrow with the following command:
select hstore_to_json_loose(hstore('"date"=>"2016-06-24"'))->>'date'

It's hard to be sure, but I think this might be the same as bug #13906
which was fixed in 9.4.6. If updating doesn't resolve it for you, please
resubmit with a more precise description of what's wrong.

regards, tom lane

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

#3Alvaro Herrera
alvherre@2ndquadrant.com
In reply to: Noname (#1)
Re: BUG #14213: bug in hstore_to_json_loose() function

knut@wehrle.org wrote:

I get an arrow with the following command:

select hstore_to_json_loose(hstore('"date"=>"2016-06-24"'))->>'date'

The problem is, that the function is not generating an ISO date string but a
mathematical formula: 2016 - 06 - 24 = 1986!

Probably this is the intended way to handle this kind of data, but then the
'->>' operator would be buggy.

Knut replied to the moderation notice to indicate that 9.4.8 fixed the
issue, and asked for a version log. Here's the git repository:
https://git.postgresql.org/gitweb/?p=postgresql.git

--
�lvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs