Mind that currently zero='' should be interpreted as zero='(please choose a value)'. the value '' is not in the db and will not pass validation. It s just a place holder. Only if IS_NULL_OR(IS_IN_DB(...zero='')) then the value '' can pass validation.
On Feb 4, 9:25 am, Jonathan Lundell <jlund...@pobox.com> wrote: > On Feb 4, 2010, at 7:08 AM, mdipierro wrote: > > > I do not really have an opinion on this. I am only reluctant to > > changes in behavior. > > Anyway, I am prepared to make this change (zero=None by default). I > > would like to know that all major contributors are on board so that > > you can answer the emails when users complain instead of me. ;-) > > > Anybody who has an opinion about this should post here or email me > > personally. > > I prefer zero=None as the default, on the grounds that it seems more logical > for the default case to not include items that aren't actually in the > database. Least surprise. > > OTOH, it's not a high priority for me, since it's easy enough to override > either way. > > > > > Executive Summery: > > > There is a proposal to default IS_IN_SET(zero=None) and > > IS_IN_DB(zero=None) so that dropdown select option NO LONGER will have > > a default black option. Currently, by default, when you create a new > > record the blank option is selected and, if you do not change it and > > if you do not allow IS_NULL, you get an error message. With the > > proposed change, when you create a new record all select/options will > > - by default - select the first alphabetical value unless you change > > it. > > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
