> > 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 >
First, I don't think this is the proposal. The proposal was to manipulate the form object itself after the form is created, but before it is serialized in the view (i.e., set the HTML "readonly" attribute of the input widget). Second, even something like the above wouldn't be a problem for concurrent users, as the above would all happen within a single request and therefore only apply to that one request. Setting a field to writable in one request does not affect it another request. Anthony --
