I understand and it is a bug. Could you please open a ticket about this?
On Saturday, 12 October 2013 09:27:45 UTC-5, Adi wrote:
Thanks Massimo. I'm talking about the automatic search query above
smartgrid that gets created when boolean field is selected as a filter. It
gets created as
opened: http://code.google.com/p/web2py/issues/detail?id=1718
On Sun, Oct 13, 2013 at 8:39 AM, Massimo Di Pierro
massimo.dipie...@gmail.com wrote:
I understand and it is a bug. Could you please open a ticket about this?
--
Resources:
- http://web2py.com
- http://web2py.com/book
Thanks Massimo. I'm talking about the automatic search query above
smartgrid that gets created when boolean field is selected as a filter. It
gets created as table.field = on. So that one works, but != on doesn't
seem to work.
On 2013-10-11 11:25 PM, Massimo Di Pierro massimo.dipie...@gmail.com
Can you please open a ticket about this?
On Saturday, 12 October 2013 09:27:45 UTC-5, Adi wrote:
Thanks Massimo. I'm talking about the automatic search query above
smartgrid that gets created when boolean field is selected as a filter. It
gets created as table.field = on. So that one works,
done: http://code.google.com/p/web2py/issues/detail?id=1718
On Sat, Oct 12, 2013 at 2:33 PM, Massimo Di Pierro
massimo.dipie...@gmail.com wrote:
Can you please open a ticket about this?
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
-
there are the only valid queries involving a boolean:
table.field == True
table.field == False
table.field == None
table.field != True
table.field != False
table.field != None
On Friday, 11 October 2013 21:19:52 UTC-5, Adi wrote:
Search:
table.field = on (shows rows with T)
table.field !=
6 matches
Mail list logo
