I updated to the current tip, changeset c98c7012176f, and now things
work again the way they should: a MySQL time value of 00:00:00 is
returned by DAL as datetime.time(0, 0) as it should be.
Thank you.
I will look. If this is a web2py issue it will be fixed.
On Sep 14, 4:14 pm, Fred fre...@gmail.com wrote:
I've got an application that stores time of day and midnight
(00:00:00) is a valid time that sometimes needs to be stored and
retrieved. That used to work fine in an old release of web2py
Would it be possible to look into the fact that when storing 24:00:00
and read out it will be converted into a value of 1 day instead of 24:00:00.
Kenneth
I will look. If this is a web2py issue it will be fixed.
On Sep 14, 4:14 pm, Fredfre...@gmail.com wrote:
I've got an application that
I think this is fixed in trunk. If ok I will post 1.84.5 tomorrow.
On Sep 14, 4:14 pm, Fred fre...@gmail.com wrote:
I've got an application that stores time of day and midnight
(00:00:00) is a valid time that sometimes needs to be stored and
retrieved. That used to work fine in an old release
4 matches
Mail list logo
