Re: Need schema design advice

could you provide a brief explanation of EAV ?

thx
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business of Sender. This transmission is of a confidential nature and Sender does not endorse distribution to any party other than intended recipient. Sender does not necessarily endorse content contained within this transmission.

> Date: Sun, 12 Oct 2008 20:22:14 +0100
> From: sam(at)samason(dot)me(dot)uk
> To: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Need schema design advice
>
> On Sun, Oct 12, 2008 at 08:12:40PM +0100, I wrote:
> > As always, it's a trade off between what you're optimizing for. If
> > you're adding more preference types then go for a EAV style design, if
> > you're going to want to add more details about the preferences (this
> > does seem to be the common case, which is why most people here stay
> > away from EAV designs)[...]
>
> oops, got distracted and forgot to finish this sentence!
>
> ...then you're better off with a non-EAV style design.
>
>
> Sam
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general

_________________________________________________________________
Stay up to date on your PC, the Web, and your mobile phone with Windows Live.
http://clk.atdmt.com/MRT/go/msnnkwxp1020093185mrt/direct/01/