Re: Hstore vs simple K:V

Richard Albright <ralbright@xxxxxxxxxxxxxxxx> · Wed, 06 Jun 2012 17:03:50 -0400



    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
      

      Email: ralbright@xxxxxxxxxxxxxxxx