Adrian von Bidder <[email protected]> writes: > Ideas & comments?
For what it's worth, I'd think that the best sort of audit would be something done in the database itself, since it would audit any changes whether done through any interface. It depends on the database involved, but for example, in PostgreSQL you could establish audit rules on the relevant tables that copied old row values into a mirror audit table whenever they changed. You can put the audit tables off in a different schema (which also lets you keep the same table names) to avoid them being visible by default to normal users/applications in the database. -- David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
