Hi - I am v.new to web2py (and python) and I am trying to find if there is any reason I should not try it as an alternative to Java servlets. I think I appreciate the savings I could make but I don't want to invest a lot of time and then find an unacceptable constraint. My apps are commercial, need to be robust but are not high volume enough for things like load balancing, etc.
My concern at the moment is how to prevent updates being lost if 2 users are simultaneously updating the same row. This may seem unlikely but I have always included a version number or last_action_timestamp in every table to allow update table set.... where id=my_record.id and version=my_record.version. In my jargon this is "optimistic locking". How should I implement this in web2py? web2py always includes an id column (which is what I would do). Depending on the answer to the above question, would it be a good idea to also include a version number or last action timestamp and automatically check that. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
