Re: Custom Fields Database Architecture - Mailing list pgsql-general

From Greg Stark
Subject Re: Custom Fields Database Architecture
Date
Msg-id 407d949e0906160450h53579258g97391d2dde99c677@mail.gmail.com
Whole thread Raw
In response to Custom Fields Database Architecture  (Gnanam <gnanam@zoniac.com>)
Responses Re: Custom Fields Database Architecture
List pgsql-general
On Mon, Jun 15, 2009 at 2:04 PM, Gnanam<gnanam@zoniac.com> wrote:
>
> I also read some article which talks about the type of patterns:
> 1. Meta-database
> 2. Mutating
> 3. Fixed
> 4. LOB
>
> My question here is, what is the best approach to define the architecture
> for custom fields. Performance should not be compromised.

The reason there are multiple patterns are because the best approach
depends very much on the specifics of your needs.

For all David's dogma there are use cases where EAV is the best fit.
But there are downsides and if those downsides are a problem then one
of the other patterns may be a better fit.

--
greg
http://mit.edu/~gsstark/resume.pdf

pgsql-general by date:

Previous
From: Frank Heikens
Date:
Subject: Re: pg_relation_size, relation does not exist
Next
From: Whit Armstrong
Date:
Subject: Re: pg_relation_size, relation does not exist