Because we don't expect all users to use MySQL. Also, if you are two open the edit profile form in two different browsers, and click Save - one seconds after the other. In normal applications, the last one in wins. We want to prevent that - therefore you're likely see an error in the 2nd one because the first one has already updated the version.
Matt On 10/22/07, dev dev <[EMAIL PROTECTED]> wrote: > Why do we need to define "version" property in the User model object if > MySQL already supports optimistic locking (by default) using multiversioning > technique? > > Thanks > dev > -- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
