From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | ShadowGhost <violin05082003(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Extension for PostgreSQL cast jsonb to hstore WIP |
Date: | 2024-04-02 12:47:57 |
Message-ID: | 2439b6cf-4dca-a229-2fcd-ab00ef9a400c@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2024-04-02 Tu 07:07, ShadowGhost wrote:
> Hello all.
> Recently, when working with the hstore and json formats, I came across
> the fact that PostgreSQL has a cast of hstore to json, but there is no
> reverse cast. I thought it might make it more difficult to work with
> these formats. And I decided to make a cast json in the hstore. I used
> the built-in jsonb structure to create it and may have introduced
> methods to increase efficiency by 25% than converting the form
> jsonb->text->hstore. Which of course is a good fact. I also wrote
> regression tests to check the performance. I think this extension will
> improve the work with jsonb and hstore in PostgreSQL.
> If you've read this far, thank you for your interest, and I hope you
> enjoy this extension!
>
One reason we don't have such a cast is that hstore has a flat
structure, while json is tree structured, and it's not always an object
/ hash. Thus it's easy to reliably cast hstore to json but far less easy
to cast json to hstore in the general case.
What do you propose to do in the case or json consisting of scalars, or
arrays, or with nested elements?
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bharath Rupireddy | 2024-04-02 12:48:33 | Re: Synchronizing slots from primary to standby |
Previous Message | Alexander Korotkov | 2024-04-02 12:31:40 | Re: [HACKERS] make async slave to wait for lsn to be replayed |