Thank you! I'll try. 2009/8/8 mdipierro <mdipie...@cs.depaul.edu>
> > fixed in trunk, please give it a try. somebody should test db2 too > since it is treated differently. > > On Aug 8, 5:24 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > I think we must replace strftime with isoformat in sql.py. I will take > > care of it. > > > > Massimo > > > > On Aug 8, 4:37 am, 陶艺夫 <artman...@gmail.com> wrote: > > > > > You are right! As far as I know, the limitation of strftime still > remains in > > > the newest version of python under win32 (and any other platforms?). > > > So I think should web2py try to format date by code rather than > strftime > > > function. Because the limitation of strftime datetime function will > confine > > > us to use datetime in the database late than 1899-12-31, at least under > > > win32. It's sort of ridiculous. > > > > > 2009/8/8 mdipierro <mdipie...@cs.depaul.edu> > > > > > > Which python version? This may be a python issue, not a web2py issue. > > > > > > On Aug 7, 2:22 pm, 陶艺夫 <artman...@gmail.com> wrote: > > > > > Hi, my app got an error in "db(db.person.birth_date>=_date)" , when > the > > > > > _date had a value < '1900-01-01'. That's for python's strftime > > > > constraint. > > > > > I found chaging _date to _date.isoformat() would work, and I had to > > > > search > > > > > whole my app to make the change. > > > > > Or is there a better solution? > > > > > > > Thanks. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@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 -~----------~----~----~----~------~----~------~--~---
