Don't be. A false positive is always better than a bug unchecked. :-)
On Friday, 26 April 2013 07:18:42 UTC-5, Cliff Kachinske wrote: > > I think I caused the problem. Yesterday morning I installed system > updates but I didn't reboot until this morning. > > Now everything is working. > > So I am both embarrassed and apologetic right now. Sorry for wasting > everybody's time. > > Cliff Kachinske > > On Friday, April 26, 2013 7:03:09 AM UTC-4, Anthony wrote: >> >> Cliff, can you provide some table definitions and a full query that >> reproduces the problem? >> >> On Thursday, April 25, 2013 10:13:09 PM UTC-4, Cliff Kachinske wrote: >>> >>> The &= is working on other query clauses, just not the ones I said were >>> giving problems. >>> >>> I'll get dal.py from trunk tomorrow AM and try it. >>> >>> @Massimo, perhaps I wasn't clear. This query = date_field < "4/1/13 >>> and 4/5/13" stuff isn't what I wrote, it's what dal.py emitted. >>> >>> On Thursday, April 25, 2013 9:29:19 PM UTC-4, Anthony wrote: >>>> >>>> On Thursday, April 25, 2013 7:11:17 PM UTC-4, Massimo Di Pierro wrote: >>>> >>>>> &= is now in trunk but one cannot do >>>> >>>> >>>> I think it's always been possible to do &= with Query objects because >>>> the __and__ method is defined. What was recently added was __rand__ and >>>> __ror__, which according to >>>> http://docs.python.org/2/reference/datamodel.html#emulating-numeric-types >>>> allows >>>> binary operations with swapped operands. So, if you have A & B, and A >>>> doesn't implement the __and__ method but B implements the __rand__ method, >>>> then it will execute B.__rand__(A). Not sure what the use case is for >>>> queries, though. >>>> >>>> Anthony >>>> >>> -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
