I think the solution to this problem should be solved into the data-model. That is how the big ERP systems are resolving this issue. * The proposed solution to record every change with a insert plus time-stamp will generate to much data overhead that you do not want. You may think of this solution for statical data only, that isn't changing to much. * The proposed solution to store the PDF files with meta-data could be a solution but still the system is not reflecting the past state! and you definitely want that too.
The solution must be found in changing the data-model. There where data must NOT be changed anymore, there should be no reference table where the data is pulled from. It should be stored "hard" without a link. E.g. for invoices, table account_invoice -> field create_uid and write_uid are linking to res_users -> id field. Same for the partner_id and address_invoice_id, they should not be linked to the reference table, but stored with the real data in the invoice table. This would be a big redesign of the application as many sessions are linked to this table and needs to be reworked. So for now I would suggest to store every change in customer and user records with an update and time stamp. (This data isn't changed that much, right) The account_invoice table has already create_date timestamp write_date timestamp Resulting in that the application can find the right record back based on the timestamp in the user and partner table. The same should be done for Items/Products and there pricelist. Hope the development team would consider a redesign for the next version! ------------------------ www.veritos.nl -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=31475#31475 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
