No clue if this would work, but... Could you create a sort of a wrapper object that basically just takes two foreign keys -- one to a "production" content object and one to a "staging" object? Then when you serve up content, instead of calling on a content object, you call on a wrapper object, determine whether the production or staging content object is being requested, and return that one?
The other option I can think of is a field in the content object that indicates whether it's in staging or production status, but I don't know how you'd enforce that only one would be active at once. On Jun 6, 8:13 am, oggie rob <[EMAIL PROTECTED]> wrote: > Hi all, > I have some models and need to add the capability of versioning the > data. Basically for each object that represents a page, I want to have > a "running" version and an "editing" version of the same page, so that > users can see the "approved" version yet I can work on a newer one. > (I've found this called staging but it didn't appear to be as widely > used as I expected - if I'm using the wrong term, please let me know.) > I've considered a few things but nothing I've fiddled with has been > terribly elegant. > > So if you have thought through the same problem and have any > suggestions, please let me know. Thanks! > > -rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
