Okay, reading the new transaction docs a little closer it looks like you've implemented method (2) in my message above. Seems to me like this is the necessary method, the only sane thing to do in web context.
However, since the transactions apply only in short-lived context of when user is saving changes and they've being applied back to the database there still arises question of how to prevent one user from overwriting another's changes without knowing. This type of transaction support does nothing to prevent that. Seems to me like incorporating some sort of "overwrite-prevention" logic into the Django-framework is best method of solving the problem. Many developers _ need_ this functionality and it should be _desirable_ even when it's not absolutely necessary. Aren't uneditable timestamps already part of every Django-table? Arent' they sufficient to provide necessary versioning info? (I.e., if timestamp in db is different from timestamp of record being updated or deleted then record has been modified by intermediary user and -- at a minimum -- warning should be provided, fuller logic would allow choice of completing or abandoning the transaction, auto-retrieval of intermediately saved record for comparison, etc.). -- Herb --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
