[email protected] wrote:
The most important thing is to get a PDF+metadata immutable system setup.
Beyond that, as far as what you're suggesting to do with SQL tables, I would never recommend to any company to do it that way.
Even if the indexing could handle it (of course indexing would take much longer), it makes debugging things in the tables extremely difficult. The idea is to keep your running application as simple and streamlined as possible. Move any extraneous complexity to other table sets.
Because there is currently a very significant bug in the audittrail
module I was looking at implementing the audittrail functionality as
triggers on tables instead of via python functions.
Your method of keeping a historical records in secondary tables could be
handled the same way, I suppose. Though making that historical data
available to the rest of the application would then take a fair bit of work.
_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users
