From: Richard Albright <ralbright@insiderscore.com>
To: pgsql-admin@postgresql.org
Subject: Re: Hstore vs simple K:V
Date: Wed, 06 Jun 2012 17:03:50 -0400
Message-ID: <4FCFC5B6.1070300@insiderscore.com> (raw)
In-Reply-To: <1339014818.64273.YahooMailNeo@web161505.mail.bf1.yahoo.com>
References: <1339014818.64273.YahooMailNeo@web161505.mail.bf1.yahoo.com>
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@insiderscore.com <mailto:ralbright@insiderscore.com>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ralbright@insiderscore.com
Subject: Re: Hstore vs simple K:V
In-Reply-To: <4FCFC5B6.1070300@insiderscore.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox