On 7 Nov 2013, at 9:20 AM, Massimo Di Pierro <[email protected]> wrote:
> One can do > > request.now = request.utcnow > > For applications which are usually accessed from the same time-zip as the > server the current server makes it easier to set dates. I'm of course influenced by my own applications, with global clients and cloud-based servers; UTC is the only way I can correlate timestamps across all events. And even with local clients and servers I think that at least in some environments daemon processes (ie web servers) see UTC rather than local time. It seems safest to work entirely in UTC, and convert to local time for display as required. Timezones are a real rats' nest of problems, especially with daylight/standard changes. > > > On Thursday, 7 November 2013 10:14:03 UTC-6, Jonathan Lundell wrote: > Digressing slightly: it seems to me that one would ordinarily almost always > want to use datetime.utcnow() rather that datetime.now(); likewise > request.utcnow. At least in the database. > > > On 7 Nov 2013, at 8:03 AM, Anthony <[email protected]> wrote: > >> On Thursday, November 7, 2013 10:06:57 AM UTC-5, Jonathan Lundell wrote: >> On 7 Nov 2013, at 6:00 AM, Anthony <[email protected]> wrote: >> >>> Actually, my original explanation wasn't quite correct -- I made the >>> corrections in the original post (same conclusion though -- #2 should be >>> preferred, but they should both result in nearly the same value). I don't >>> see how using datetime.now would lead to the error you are getting, but go >>> ahead and make the change and see if it helps. >> >> What was the correction? Seems to me if #1 works at all it's because it's >> getting recognized as a function and called; str() doesn't call it, at least >> in my testing. >> >> I made the correction directly to the original reply. You've got it -- if >> the value inserted is a callable, the DAL calls it to generate a value. >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
