On Tuesday, July 17, 2012 5:29:51 PM UTC+8, Anthony wrote: > > 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). >
Yes, this will work fine. Sorry, I was referring to db.table.field.writable = False # change the field to writable false > 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. > I am not sure if I understand this for db.table.field.writable. The change is occurring within the shared DAL object. Is it not? Best Regards -Amit --
