You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to be sufficient to change DBDate::ISO_DATE to 'yyyy-MM-dd' and the corresponding formats in DBDateTime as well. This should ensure correct four digit rendering (see http://userguide.icu-project.org/formatparse/datetime).
Related issues
This might be related to #9288. And there is another issue when using dates before 1000, see #9133
The text was updated successfully, but these errors were encountered:
Thanks for raising this. I see you've referenced the two issues I was going to reference. Do you think this is a different issue to #9133 specifically?
I'm quite confident that it is different but not independent from #9133, as in my example I use a timestamp - which is not handled by the function that causes the issue in #9133. I suppose we can fix this issue which will allow correct creation of year 1 and alike by passing a timestamp. But this won't solve the other issue (passing a date string).
Affected Version
Framework Version 4, tested on 4.6.0
Description
Constructing certain dates is not working properly with DBDate and DBDatetime.
Steps to Reproduce
This is due to this php behaviour:
Proposed solution
It seems to be sufficient to change DBDate::ISO_DATE to 'yyyy-MM-dd' and the corresponding formats in DBDateTime as well. This should ensure correct four digit rendering (see http://userguide.icu-project.org/formatparse/datetime).
Related issues
This might be related to #9288. And there is another issue when using dates before 1000, see #9133
The text was updated successfully, but these errors were encountered: