A grid search causes an exception when a user enters an unexpected field
type.
I have this field:
Field('gender', 'integer', default=0,
requires=IS_IN_SET([(0,'Unknown'), (1, 'Male'), (2, 'Female')])
Since they are represented as a string (ie Male) on screen, the user may
attempt a search like *"gender is 'Male'"* (whereas the correct but
counter-intuitive term is "*gender is 1*") which results in an error:
ValueError: invalid literal for int() with base 10: 'Male'
Perhaps there's a better way for grid search to handle exceptions like
these? Or maybe the query popup should list the options provided for by the
field's default validator?
