| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Cc: | obartunov(at)gmail(dot)com, Andres Freund <andres(at)2ndquadrant(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-03-04 10:18:46 |
| Message-ID: | CAM3SWZQwE97S-U5FTjqvnk0nYnHHOa2GieT0h0s7u8x7+gNAxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 4, 2014 at 2:07 AM, Teodor Sigaev <teodor(at)sigaev(dot)ru> wrote:
> No, type of this storage describes type of keys. For gin_hstore_ops each key
> and each value will be stored as a text value. The root of problem is a
> JavaScript or/and our numeric type. In JavaScript (which was a base for json
> type) you need explicitly point type of compare to prevent unpredictable
> result.
That's what I meant, I think. But I'm not sure what you mean:
Native Chrome JavaScript.
Copyright (c) 2013 Google Inc
25 == 25
=> true
25 == 25.0
=> true
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-03-04 10:18:56 | Re: jsonb and nested hstore |
| Previous Message | Teodor Sigaev | 2014-03-04 10:18:00 | Re: jsonb and nested hstore |