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.
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.fuchs||Date: 2012-06-07 07:47:21|
|Subject: Re: Can schemas be ordered regarding their creation time ?|
|Previous:||From: Amador Alvarez||Date: 2012-06-06 20:44:46|
|Subject: Re: Can schemas be ordered regarding their creation time