| From: | "Leif B(dot) Kristensen" <leif(at)solumslekt(dot)org> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Asssociative Arrays: Best practices / snippets? |
| Date: | 2009-05-23 10:22:24 |
| Message-ID: | 200905231222.24055.leif@solumslekt.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Saturday 23. May 2009, Stefan Keller wrote:
>I have a use case where the I want to put an unforeseable number of
>key/value pairs in a column.
>Now, PostgreSQL has arrays as first class types.
>Are there any best practices and snippets (preferrably in plpgsql) for
>handling key/value pairs?
>-- S.
The «best practice» here is probably rethinking your design. Storing
an «unforeseeable number of key/value pairs in a column» is a blatant
violation of good database design principles.
Rodrigo posted this link a few hours ago:
http://joecelkothesqlapprentice.blogspot.com/2006/04/using-one-table-vs-many.html
--
Leif Biberg Kristensen | Registered Linux User #338009
Me And My Database: http://solumslekt.org/blog/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Filip Rembiałkowski | 2009-05-23 11:24:28 | Re: Asssociative Arrays: Best practices / snippets? |
| Previous Message | Alban Hertroys | 2009-05-23 10:05:51 | Re: Code tables, conditional foreign keys? |