EAV or not to EAV?

Поиск
Список
Период
Сортировка
От Reg Me Please
Тема EAV or not to EAV?
Дата
Msg-id 200711220948.36142.regmeplease@gmail.com
обсуждение исходный текст
Ответы Re: EAV or not to EAV?
Re: EAV or not to EAV?
Список pgsql-general
Hi all.

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.

Is there a better idea than mine? I hope so.

--
Reg me Please
<Non quietis maribus nauta>

В списке pgsql-general по дате отправления:

Предыдущее
От: Ottavio Campana
Дата:
Сообщение: Re: Read-only availability of a standby server?
Следующее
От: Devrim GÜNDÜZ
Дата:
Сообщение: Re: POLL: Women-sized t-shirts for PostgreSQL