EAV or not to EAV?
От
Reg Me Please
Тема
EAV or not to EAV?
Дата
Msg-id
200711220948.36142.regmeplease@gmail.com
Список
Дерево обсуждения
EAV or not to EAV? Reg Me Please <regmeplease@gmail.com>
Re: EAV or not to EAV? Jeff Davis <pgsql@j-davis.com>
Re: EAV or not to EAV? Oleg Bartunov <oleg@sai.msu.su>
backup of postgres scheduled with cron "Sorin N. Ciolofan" <ciolofan@ics.forth.gr>
Re: [ADMIN] backup of postgres scheduled with cron "Marco Bizzarri" <marco.bizzarri@gmail.com>
Re: [ADMIN] backup of postgres scheduled with cron "Sorin N. Ciolofan" <ciolofan@ics.forth.gr>
Re: [ADMIN] backup of postgres scheduled with cron "Marco Bizzarri" <marco.bizzarri@gmail.com>
Re: [ADMIN] backup of postgres scheduled with cron Andrew Sullivan <ajs@crankycanuck.ca>
Re: [ADMIN] backup of postgres scheduled with cron "Marco Bizzarri" <marco.bizzarri@gmail.com>
Re: [ADMIN] backup of postgres scheduled with cron Andrew Sullivan <ajs@crankycanuck.ca>
Re: backup of postgres scheduled with cron Frank Wittig <fw@weisshuhn.de>
Re: backup of postgres scheduled with cron "Sorin N. Ciolofan" <ciolofan@ics.forth.gr>
Re: backup of postgres scheduled with cron jef.peeraer@telenet.be
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
В списке pgsql-general по дате отправления
