Re: Re: database.py update

>>I would suggest setting it to infinite instead of the current time.
> 
> Good point.  Either that or using a different query altogether.  
> Which approach do you think is more elegant?

By far the most normal case is working with the most recent
data and that should work fine no matter what the user does
with their clock.

I have no particular feelings over how this should be implemented
as long as the normal case is robust and always works correctly.

Roger


-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar