pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedHstore vs simple K:V
2+ messages / 2 participants
[nested] [flat]
* Hstore vs simple K:V
@ 2012-06-06 20:33 A J <s5aly@yahoo.com>
0 siblings, 1 reply; 2+ messages in thread
From: A J @ 2012-06-06 20:33 UTC (permalink / raw)
To: pgsql-admin
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.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Hstore vs simple K:V
@ 2012-06-06 21:03 Richard Albright <ralbright@insiderscore.com>
parent: A J <s5aly@yahoo.com>
0 siblings, 0 replies; 2+ messages in thread
From: Richard Albright @ 2012-06-06 21:03 UTC (permalink / raw)
To: 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@insiderscore.com <mailto:ralbright@insiderscore.com>
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2012-06-06 21:03 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2012-06-06 20:33 Hstore vs simple K:V A J <s5aly@yahoo.com>
2012-06-06 21:03 ` Richard Albright <ralbright@insiderscore.com>
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