I understand the proposed procedure is as follows: 1. change db table field to writable 2. make the form as needed 3. change back db table field to not writable
Suppose there are two concurrent users now, A and B, and they execute the above procedure. The concurrent scheduling is done by the server; one possible sequence is: A 1, B 1, B 2, B 3, <problem occurs> A 2, A 3. At the point of <problem occurs>, the db field is not writable and so the form will not be correct. On Tue, Jul 17, 2012 at 12:46 PM, Anthony <abasta...@gmail.com> wrote: > Can you elaborate? > > > On Tuesday, July 17, 2012 12:24:37 AM UTC-4, amit wrote: >> >> Old thread, but this would trigger a race condition in case of multiple >> concurrent users. >> >> On Friday, June 17, 2011 5:12:27 AM UTC+8, JayShaffstall wrote: >>> >>> I'd been thinking I needed to do that between form creation and the >>> accepts call, but you're right, it works even after that point. I >>> make the call to auth.register, and then modify the readonly >>> attribute, and it works fine. >>> >>> Thanks! >>> Jay >>> >> -- > > > > --
