| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | rob(at)marjot-multisoft(dot)com |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: generic modelling of data models; enforcing constraints dynamically... |
| Date: | 2009-09-28 01:13:08 |
| Message-ID: | dcc563d10909271813x69e59f78g8be17b3b337d4aea@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, Sep 27, 2009 at 5:44 PM, InterRob <rob(dot)marjot(at)gmail(dot)com> wrote:
> Oliver,
> Would you say it is not valid for proposition 2 (people wanting to be able
> to quickly add (and remove?) attributes) because within the relational model
> this can be done reasonably well?
Actually that's what I think it's best at, as long as you aren't
trying to get fancy. We have a part of an intranet type app that lets
users upload table formatted data that's like a freeform spreadsheet
and we use EAV to store the data for that. There's no FK or other
relational stuff.
The problems start to pile up when you try to do something exciting,
interesting, fascinating or other 'ings...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-09-28 01:22:47 | Re: PostgreSQL reads each 8k block - no larger blocks are used - even on sequential scans |
| Previous Message | Justin Pryzby | 2009-09-27 23:57:56 | dump time increase by 1h with new kernel |