From: David Fetter <david@fetter.org>
To: mark overmeer <markovermeer@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: schema design question
Date: Sun, 19 Aug 2007 13:23:34 -0700
Message-ID: <20070819202334.GN28490@fetter.org> (raw)
In-Reply-To: <ea41f7570708191313t26680a39yfb14760fd00c5fcd@mail.gmail.com>
References: <ea41f7570708190619u6daf7cep96430d20566d6159@mail.gmail.com>
<20070819181216.GK28490@fetter.org>
<20070819182658.GC25214@uio.no>
<ea41f7570708191313t26680a39yfb14760fd00c5fcd@mail.gmail.com>
On Sun, Aug 19, 2007 at 10:13:08PM +0200, mark overmeer wrote:
> Hi,
>
> 2007/8/19, Steinar H. Gunderson <sgunderson@bigfoot.com>:
> >
> > As a general database design paradigm, though, I fully agree with
> > you. Databases are databases, not glorified OO data stores or
> > hash tables.
>
> I don't want to use it as an OO data store, I use the filesystem for
> that. The intended use is to search for the right object. Since it
> has separate data structures for searching (indexes) I guess that is
> one of its functions.
>
> However, it still doesn't answer my question about the EV model
> (where each attribute is given its own table).
The answer to EAV modeling, is, "DON'T!"
Cheers,
David (who, if he were greedy, would be encouraging EAV modeling
because it would cause guaranteed large consulting income later)
--
David Fetter <david@fetter.org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
Consider donating to PostgreSQL: http://www.postgresql.org/about/donate
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: david@fetter.org, markovermeer@gmail.com
Subject: Re: schema design question
In-Reply-To: <20070819202334.GN28490@fetter.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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