Skip site navigation (1) Skip section navigation (2)

Re: Hstore vs simple K:V

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 (view raw or flat)
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>

In response to

pgsql-admin by date

Next:From: hari.fuchsDate: 2012-06-07 07:47:21
Subject: Re: Can schemas be ordered regarding their creation time ?
Previous:From: Amador AlvarezDate: 2012-06-06 20:44:46
Subject: Re: Can schemas be ordered regarding their creation time ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group