Details
-
Bug
-
Resolution: Invalid
-
P2: Important
-
5.9.1
-
None
Description
See attached example.
[ 0.000 D] parseDate - 7-Jun-11->Wed Jun 7 00:00:00 1911 GMT+0100 [ 0.000 D] parseDate - 6-Jun-11->Tue Jun 6 00:00:00 1911 GMT+0100 [ 0.000 D] parseDate - 5-Jun-11->Mon Jun 5 00:00:00 1911 GMT+0100 [ 0.000 D] parseDate - 4-Jun-11->Sun Jun 4 00:00:00 1911 GMT+0100 [ 0.000 D] parseDate - 3-Jun-11->Invalid Date [ 0.000 D] parseDate - 2-Jun-11->Invalid Date [ 0.000 D] parseDate - 1-Jun-11->Invalid Date [ 0.001 D] parseDate - 31-May-11->Wed May 31 00:00:00 1911 GMT+0100 [ 0.001 D] parseDate - 30-May-11->Tue May 30 00:00:00 1911 GMT+0100 [ 0.001 D] parseDate - 29-May-11->Mon May 29 00:00:00 1911 GMT+0100 [ 0.001 D] parseDate - 28-May-11->Sun May 28 00:00:00 1911 GMT+0100 [ 0.002 D] parseDate - 27-May-11->Sat May 27 00:00:00 1911 GMT+0100
Attachments
| For Gerrit Dashboard: QTBUG-63072 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 206806,3 | QDateTimeParser: reject all short values in fixed-width fields | dev | qt/qtbase | Status: MERGED | +2 | 0 |