Randall Nortman schrieb: > The typical modern way of dealing with this on the web -- if you deal > with it at all -- is opportunistic locking, where before you save > changes you check to see if any updates were made since the data was > originally presented to the user.
I noticed web apps created with Oracle Designer were doing this and I guess that's the only reasonable solution. Since there is no standard way of saving objects in plain TG, you must do this manually - it's not so difficult. Concerning Sprox, Catwalk2 or Rum, I don't know if they are doing this already, but if not they should do it. -- Christoph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
