| From: | Richard Albright <ralbright(at)insiderscore(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Hstore vs simple K:V |
| Date: | 2012-06-06 21:03:50 |
| Message-ID: | 4FCFC5B6.1070300@insiderscore.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
You don't need to do an entity attribute value model in a separate table
to include mutliple key value pairs. since an hstore is schemaless, you
can include them all in one column for a particular row.
On 06/06/2012 04:33 PM, A J wrote:
> What are the key benefits of using hstore over simple K:V storage in
> Postgres where you split the key in its own column and value in its
> own column ?
>
> Thank you for any inputs.
--
*Rick Albright*
Senior Quantitative Analyst
Web: www.insiderscore.com <https://www.insiderscore.com/>
Email: ralbright(at)insiderscore(dot)com <mailto:ralbright(at)insiderscore(dot)com>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hari.fuchs | 2012-06-07 07:47:21 | Re: Can schemas be ordered regarding their creation time ? |
| Previous Message | Amador Alvarez | 2012-06-06 20:44:46 | Re: Can schemas be ordered regarding their creation time ? |