database - django AuditTrail vs Reversion -

I am working on a new web app, where I need to make changes to the database for table audit. The purpose of such audit tables is that in a real physical audit later, what happened in a situation that we can edit, what would be a complex calculation of what was and what was the status of DB while editing, then most audit tables will be written And will not be read. Sometimes the report may be generated.

I have examined the solution available

1. - Simple and that is the reason I am tilting towards it, I can understand it as a single file code.
2. - It looks simple enough to use but it is not certain how easy it will be to modify it if necessary.
3. I feel very complicated and very much for my needs

I have not tried any of these, so I had to know some real experience and Which one should I use. Like who uses a fast space, is easy to expand and maintain?

Personally I audit table is populated in database and triggers in order to query any change from the query window also ad hoc Be archived. I do not consider an audit solution that is not based in the database itself. This is important because those who are making malicious changes in databases or fraud can not do this through the web interface but on the backend directly. Excess of this material is from dissatisfied or carefree employees compared to herrs. If you are already using an ORM, then your data is in danger because the permissions are on the table level, instead they are at the SP level where they are. Therefore, it is also important that you capture any possible change on whatever GTI is from. We have a dynamic process that is run to create audit tables, whenever new tables are added to the database. Since our audit tables only make changes and do not have complete records, whenever we add a field, they do not need to change them. Also, while evaluating potential solutions, make sure that you understand how hard it would be to once again return the data to undo the specific change, after the audit tables, you will find That this is one of the most important things for them that you have to do. Also consider how difficult it would be to maintain information as database schema changes.

Choosing a solution because it is easy to understand, this is usually not a good idea. After meeting these requirements, safety, etc., your selection criteria should be the lowest.