The rationale is easy. The field is never a problem. The problem is the forms. If you need to list all the options, you need to gather all the options from database. That is a performance hog. Using autocomplete is better. The issue is the same for reference and list:reference.
On Jan 31, 9:21 am, Anthony <abasta...@gmail.com> wrote: > On Monday, January 31, 2011 10:02:14 AM UTC-5, DenesL wrote: > > > On Jan 28, 5:27 pm, Massimo Di Pierro <massimo....@gmail.com> > > wrote: > > > Are you suggesting we change the way the default is assigned? If so.. > > > let's duscuss this inw eb2py-developers because it is a complex > > > matter. > > > No, just pointing it out. > > web2py users can just "listify" the requires to avoid the dropdown and > > its processing. > > Something to keep it mind though. > > However, the book should at least mention that "=IS_IN_DB(...)" will require > more processing than "=[IS_IN_DB(...)]", as that may not be obvious > (particularly since the validator is applied by default without being > explicitly added to the model). > See:http://web2py.com/book/default/chapter/06?search=default+field+valida...http://web2py.com/book/default/chapter/07#Database-Validators > > Also, the IS_IN_DB validator is the default for a regular 'reference' field > as well as the 'list:reference' field. Does the 'list:reference' field have > more potential for performance problems, or is it the same issue with a > 'reference' field? > > Thanks. > > Anthony
