Priority: P2: Important
Affects Version/s: 5.15.1
Fix Version/s: None
Component/s: Core: Date/Time
Some old databases might contain invalid timestamp values due to summer time transition, i.e. "2015-03-29 02:09:11.001". The date component is valid, but the time not. QDateTime could handle this value in the past.
According to the documentation of function QDateTime::isValid()) handling of such timestamp should be still possible:
This has been broken in the latest version which makes the auto correction impossible.
The following snippet explains the differences:
The following also does not work. Value returned is not null, but isValid() returns true (which is definitely wrong)
|For Gerrit Dashboard: QTBUG-88633|
|323492,3||Return a more useful date-time on parser failure in spring-forward gap||dev||qt/qtbase||Status: MERGED||+2||0|
|324050,2||Return a more useful date-time on parser failure in spring-forward gap||6.0||qt/qtbase||Status: MERGED||+2||0|
|324051,3||Return a more useful date-time on parser failure in spring-forward gap||5.15||qt/qtbase||Status: MERGED||+2||0|