| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Oleg Bartunov <obartunov(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Teodor Sigaev <teodor(at)sigaev(dot)ru> |
| Subject: | Re: jsonb and nested hstore |
| Date: | 2014-01-31 13:57:23 |
| Message-ID: | CAHyXU0zUDp_mZKbEU2o0cKyDmrpY2kUqSQfWp0O6YCWin+NRFQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jan 31, 2014 at 4:03 AM, Oleg Bartunov <obartunov(at)gmail(dot)com> wrote:
> Hmm,
> neither me, nor Teodor have experience and knowledge with
> populate_record() and moreover hstore here is virgin and we don't know
> the right behaviour, so I think we better take it from jsonb, once
> Andrew realize it. Andrew ?
Andrew Gierth wrote the current implementation of htsore
populate_record IIRC. Unfortunately the plan for jsonb was to borrow
hstore's (I don't think hstore can use the jsonb implementation
because you'd be taking away the ability to handle internally nested
structures it currently has). Of my two complaints upthread, the
second one, not being able to populate from and internally well formed
structure, is by far the more serious one I think.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mitsumasa KONDO | 2014-01-31 13:57:44 | Re: Exposing currentTransactionWALVolume |
| Previous Message | Fujii Masao | 2014-01-31 13:56:26 | Re: Exposing currentTransactionWALVolume |