yes, there is a bug that is causing this. I will try fix it later today
On Jul 1, 9:08 am, Peter <[email protected]> wrote: > > but not show it in crud.read and SQLTABLEs > > Exactly, that is what I would expect. > > My point is that even with the setting .readable=False (and .writable > True), the field IS shown in crud.read output. > > -P > > On Jul 1, 3:50 pm, mdipierro <[email protected]> wrote: > > > This is the correct behaviours. It maens you can want to edit/update > > the field but not show it in crud.read and SQLTABLEs > > > On Jul 1, 8:04 am, Peter <[email protected]> wrote: > > > > Given this controller: > > > def vread(): > > > db.auth_user.something.readable=False > > > db.auth_user.something.writable=True > > > return dict(form=crud.read(db.auth_user,auth.user.id)) > > > > I would expect the field <something> to be suppressed in output. This > > > is not the case, but when I set *.writable* to False as well the field > > > does disappear from the crud.read output. Problem (if it is that) > > > seems to be in the underlying SQLFORM(..., readonly=True). > > > > Is this behavior correct, or have I misunderstood the semantics for > > > readable/writable... ;-) > > > This is using the 1.64.4 release. > > > > Cheers, > > > -Peter --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
