I've already got an issue open on this
(http://code.google.com/p/web2py/issues/detail?id=523) and would really
like to see it included in the trunk. My proposed change allows you to
override the default search capabilities and pass your own search
criteria in. You can provide a custom <div> that contains the html for
the search.
I'd like others to look at at it and improve upon what I've suggested.
I'm recommending that we keep the default search capabilities, but allow
the individual developer to easily override it and provide their own
mechanisms.
-Jim
On 12/2/2011 7:53 AM, Anthony wrote:
I agree -- it could use some usability improvements. Please open an
issue at http://code.google.com/p/web2py/issues/list.
On Friday, December 2, 2011 6:48:50 AM UTC-5, peter wrote:
Going back to my original problem, Anthony is right. If you define a
single filter you have to click 'and' or 'or' to get the filter to be
copied into the search. This is easy enough when one knows, but is not
exactly intuitive if one does not want to 'and' or 'or' the filter
with anything (I recognise there is an implicit true). As we have a
'clear' button, maybe clicking 'query' when there is a filter defined
and the search field is empty should cause the filter to be copied to
the search field. Other 'naive' users like myself would probably try
clicking the 'query' button but are less likely to try clicking the
and/or buttons when they have a single query.
Peter
On Dec 1, 10:02 pm, villas <[email protected]> wrote:
> Sorry to include this in the same thread, but I think it may be of
> interest to a similar audience...
>
> Given that SQLFORM.grid uses DAL smart_query...
> It seems that smart_query does not implement: 'belongs' | 'in'
>
> Is that an omission, or by design, or have I missed something?
