in retrospect this was a poor design decision, but we cannot change it for backward compatibility.
On Wednesday, 4 November 2015 23:53:05 UTC-6, Mark Graves wrote: > > Hey everyone, > > I find myself in the need for microsecond level precision for time fields > where I am querying over those fields regularly. > > As I dug into pydal and web2py's internals, I noticed that it seems to be > convention that times are truncated to H:M:S > > I'm aware I can easily store as a string and coerce or define a custom > field type or store as a datetime for the required precision. > > I'm finding that rather cumbersome. > > Am I missing something or would this be the best way to approach this? > > -Mark > > -- 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
