Is there a big advantage of MartyAlchin Historization over the django- reversion project? Has anybody compared the two approaches in detail. >From what i could understood on the django-revsion site it seems to me more complete, as it inclueds i.e. file-reversion. Plus it is easier to use as it is maintained and delivered as an app. Any expert's opinions?
david On 28 Okt., 01:15, Mike Dewhirst <mi...@dewhirst.com.au> wrote: > Todd Blanchard wrote: > > Total django noob here. Rails/PHP/WebObjects refugee here. > > > I'm starting a project where some models need to be fully versioned. > > > IOW, record update is forbidden - every save to a changed model should > > result in a new record with a new version number or timestamp along > > with identity pulled from the current authenticated user's session. > > Queries/relationships should be specified as "fetch newest" or "fetch > > history". IOW sometimes I want to traverse a relationship and just > > get the "current" record. Sometimes I want to get the history of that > > relationship. > > > Anybody done this? Got any tips? > > Marty Allchin has documented this very precisely and eloquently in > chapter 11 of his Pro Django published recently by Apress. > > Highly recommended :) > > Cheers > > Mike > > > > > Thanks, > > -Todd Blanchard --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
