Hi Raphaël, Well, first of all this is not how you find this type of solution implemented universally. And the reasoning is that the temporal archive store should be entirely standalone from the operational system for the very reason of performance. In many companies much research goes on regarding the archive and this should be kept away from the operational system which should be dealing with only current data. For companies that exist for long time you would definitely not want the archive in the operational system database. Imagine if you had ten or fifteen years or more worth of imaged documents to store. This amount of data would get very large which can have very detrimental performance impacts to the 'current' operational system. And because you can custom tune the search behavior in the temporal archive database system this amount of data does not present so much of an issue there. I have been involved with several companies that have implemented these temporal archive systems and I did not see even one of them consider having the archive as part of their operational system.
Regards, Gerry _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
