On Jan 25, 12:08 pm, Juergen Schackmann <juergen.schackm...@googlemail.com> wrote: > why do you want to create the dual tables, instead of only having one table > with a current tag that holds the old version and the current ones? and then > handle access to those via different managers? > have you also had a look at the available versioning apps?
I forgot to include this in my original post: I already have a working application and I would like to be able to add versioning support without changing the current schema. Also, I am using Admin, and I am afraid of the amount of work this would require. I am currently using a setup where each change gets logged into dual tables using plpgsql triggers, but as the content is relatively large per row, and updated quite often, while new versions aren't that common, I will get a lot of bloat in the dual tables using my current setup. And it is a bit hard to actually fetch the correct version from the dual tables... I will look into the existing versioning apps, maybe one of the will allow me to easily create this kind of setup. Thank you for the help, - Anssi -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
