Aside to Iceberg, Massimo's requires clause, which includes the
IS_NULL_OR() condition, has made it possible for me eliminate all my
db.table.field.readable=db.table.field.writable=False statements and
still get the forms to get through to the validation stage. As for
whether they will validate correctly and store correctly is yet to be
seen. I haven't been able to get that far, yet, but I'm on it right
now.
On Sep 8, 5:19 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
> Field('myinteger','integer',default=0),requires=IS_NULL_OR
> (IS_INT_IN_RANGE(-10,10)))
>
> On Sep 8, 2:48 pm, weheh <richard_gor...@verizon.net> wrote:
>
>
>
> > The saga continues ...
>
> > Unused table fields have been turned off. That gets rid of most
> > form.errors. However, some of the fields are not turned off. Those
> > fields have default values set in the Field definition. However, I'm
> > getting error messages associated with those fields. Such as:
>
> > Field('myinteger','integer',default=0)
>
> > and then after posting the form, I'll get the error message:
>
> > too big or too small!
>
> > associated with myinteger. I can turn myinteger off, but at somepoint
> > during the form processing, I want to set myinteger to 0, so I'll have
> > to turn it back on again. Anybody know why this isn't working by
> > reading the default value from the db definition?- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To post to this group, send email to web2py@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
-~----------~----~----~----~------~----~------~--~---
