| From: | Oliver Kohll - Mailing Lists <oliver(dot)lists(at)gtwm(dot)co(dot)uk> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: generic modelling of data models; enforcing constraints dynamically... |
| Date: | 2009-09-27 21:19:11 |
| Message-ID: | A69B1B88-620B-462F-B67D-24A44042B9E3@gtwm.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 27 Sep 2009, at 21:10, InterRob <rob(dot)marjot(at)gmail(dot)com> wrote:
> Peter, may I invite you to privately share some more details on the
> system you are using and the design of it? Did you implement it
> using PostgreSQL? Looking forward to your reply.
> (And with respect to your previous message: whom are you actually
> referring to by the acronym "OPs"?)
>
Or publicly? I for one would be interested hearing more. From
situations I've come across, EAV seems to be proposed when either
1) attributes are very numerous and values very sparse
2) people want to be able to quickly add (and remove?) attributes
My feeling is it's probably valid for 1, at least I haven't come
across anything better, but not for 2.
Regards
Oliver
www.gtwm.co.uk - company
www.gtportalbase.com - product
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sam Mason | 2009-09-27 21:19:42 | Re: PostgreSQL reads each 8k block - no larger blocks are used - even on sequential scans |
| Previous Message | Sam Mason | 2009-09-27 21:01:27 | Re: PostgreSQL reads each 8k block - no larger blocks are used - even on sequential scans |