Re: Application Design: Where to implement historical revisions of objects
От | Michelle Konzack |
---|---|
Тема | Re: Application Design: Where to implement historical revisions of objects |
Дата | |
Msg-id | 20070525174108.GA6097@freenet.de обсуждение исходный текст |
Ответ на | Application Design: Where to implement historical revisions of objects ("Colin Ross" <colinross@gmail.com>) |
Ответы |
Re: Application Design: Where to implement historical revisions of objects
|
Список | pgsql-php |
Hello Colin, Am 2007-05-23 13:10:42, schrieb Colin Ross: > In Practice: > An application has a model class of "PageContent" which represents the > content that is shown on a certain page. Users of the system are > authenticated, then able to edit the content. From an application design > point > of view, where should the logic and underlying system be for the management > of historical revisions. I have something similar, exactly, a Database of military data and data sets are never modified but added. So, I give each dataset a serialnumber and a revision 0. Then if the dataset was modified I change the revision to a higher number and add the whole dataset into a new row. This thing is done using trigers. Greetings Michelle Konzack Systemadministrator Tamay Dogan Network Debian GNU/Linux Consultant -- Linux-User #280138 with the Linux Counter, http://counter.li.org/ ##################### Debian GNU/Linux Consultant ##################### Michelle Konzack Apt. 917 ICQ #328449886 50, rue de Soultz MSN LinuxMichi 0033/6/61925193 67100 Strasbourg/France IRC #Debian (irc.icq.com)
Вложения
В списке pgsql-php по дате отправления: