On Wednesday, February 29, 2012 12:59:18 AM UTC+2, akaariai wrote:
> Combined with database-level triggers you can get a good audit trail.
> I have some scripts to ease maintain the DB triggers for PostgreSQL
> when using Django. I hope I will have some time to polish them for
> release, I believe they could be some use for the community.
>
> I now have a _very_ experimental shadow table management project at:
https://github.com/akaariai/pgsql_shadow_tables
I ended up rewriting the project from scratch. The above version is purely
plpgsql based, so it is usable in any project using PostgreSQL.
There are some nice features:
- You have modification history available (well, duh).
- You can "timetravel" your database.
- After schema modifications, upgrading the shadow tables should be
oneliner: select shadow_meta.update_shadow_schema('public');
See the README for more info. It might be a little hard to follow. As said,
I have not used much time for polishing the project.
Once more: it is currently in very early stages. I do not use the scripts
in production, and neither should you.
With some testing and some polishing I believe the project could be very
useful for small write volume web-apps.
- Anssi
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/V2a76BC5EeIJ.
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/django-users?hl=en.
