From: Jeff Davis <pgsql@j-davis.com>
To: Reg Me Please <regmeplease@gmail.com>
Cc: pgsql-general@postgresql.org
Subject: Re: EAV or not to EAV?
Date: Sun, 25 Nov 2007 10:01:29 -0800
Message-ID: <1196013689.24251.342.camel@jdavis> (raw)
In-Reply-To: <200711220948.36142.regmeplease@gmail.com>
References: <200711220948.36142.regmeplease@gmail.com>
On Thu, 2007-11-22 at 09:48 +0100, Reg Me Please wrote:
> I have to take into account the update history of every single
> field into a number of tables.
> Those updates can come to the future (next values) but also to the
> past (history fix) and apply only to some fields, usually not to the
> entire record.
> Every lookup in those tables is always related to a timestamp that
> normally is the current timestamp, but can also be a past timestamp.
>
> I've come up with a "traditionally regretted" EAV design with the add of
> timestamps for the history. And the related problems, some of which have
> been solved by Joe Conways's crosstab contrib.
Here are two more ideas:
1) Vertically partition the tables so that each field you want to track
is in its own table, and then track the history of those individual
tables. Then join the tables on a key that doesn't change when you need
to see the whole table. This works well if you only have a few non-key
fields per table.
2) Store a normal history, but also store a bitmap of the fields that
change in each record. You might use partial indexes to be able to
quickly select only those records where a certain field has changed.
EAV will give you many problems down the line, and I don't think it will
solve anything for you.
Regards,
Jeff Davis
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-admin@postgresql.org
Cc: pgsql@j-davis.com, regmeplease@gmail.com, pgsql-general@postgresql.org
Subject: Re: EAV or not to EAV?
In-Reply-To: <1196013689.24251.342.camel@jdavis>
* 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