just a thought... if it turns out that datetime can't retain microseconds so as not to break Calendar (and presumably user code out there) could a new field type be added to Web2py? timestamp could store a full Python datetime definition.
On Feb 21, 4:01 pm, mdipierro <mdipie...@cs.depaul.edu> wrote: > forgot about the issue. will take a second look. > > On Feb 21, 5:48 am, Carl <carl.ro...@gmail.com> wrote: > > > > > Following Dan's posting last year about the loss of microseconds when > > storing PythonDateTimeinstances in > > SQLitehttp://groups.google.com/group/web2py/browse_thread/thread/f9b8cbb660... > > I've got to this area too :) > > > Dan suggests a work-around for SQLite users based on SQLCustomType. > > > A few of questions popped up: > > > 1. is Dan' post the last on this subject (I searched Groups but one is > > never sure) > > > 2. is Dan's work-around the recommended approach for developers > > needing to maintain Python DataTime objects in a non-gae database? > > > 3. do you know if Web2py only maintains Python DataTime object's > > millisecond precision for gae? Or is it maintained for other database? > > > 4. and related to #3... is the datepicker calendar code that needs the > > millisecond precision removed broken on gae? -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
