--===============4148595452807921702==
Content-Type: multipart/alternative; boundary="94eb2c08860607c8b105540fbeb3"

--94eb2c08860607c8b105540fbeb3
Content-Type: text/plain; charset="UTF-8"

On 11 July 2017 at 17:28, Mark Johnson <mj10777@googlemail.com> wrote:

> While working on an overhaul of the QgsSpatiaLiteProvider (for Spatialite
> 4.5.0), I just completed the portion for setting the default DATE/DATETIME
> etc. only to find that for the QDateTimeEdit class, the beginning or the
> world is determined by the Act of Parliament of 1751 (Calendar Act) - which
> is a disaster for any Historical Database for any event before 1752-09-14.
>

Fortunately, historical dates and time zones are are two of QDateTime
'bugs' I fixed for Qt5. To that extent, the future is brighter for the past
in QGIS 3 :-) Sadly at the time there was no QtWidgets maintainer so the
QDateTimeEdit patch to use it didn't get in. It may have been fixed in a
recent Qt5 release though, I think I saw a patch float past sometime in the
the last year or so...

Of course, that doesn't help you right now :-)

John.

--94eb2c08860607c8b105540fbeb3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On 11 July 2017 at 17:28, Mark Johnson <span dir=3D"ltr">&=
lt;<a href=3D"mailto:mj10777@googlemail.com" target=3D"_blank">mj10777@goog=
lemail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">While work=
ing on an overhaul of the=C2=A0QgsSpatiaLiteProvider (for Spatialite 4.5.0)=
, I just completed the portion for setting the default DATE/DATETIME etc. o=
nly to find that for the QDateTimeEdit=C2=A0class, the beginning or the wor=
ld is determined by the=C2=A0Act of Parliament of 1751 (Calendar Act) - whi=
ch is a disaster for any Historical Database for any event before 1752-09-1=
4.</div></blockquote><div><br></div><div>Fortunately, historical dates and =
time zones are are two of QDateTime &#39;bugs&#39; I fixed for Qt5. To that=
 extent, the future is brighter for the past in QGIS 3 :-) Sadly at the tim=
e there was no QtWidgets maintainer so the QDateTimeEdit patch to use it di=
dn&#39;t get in. It may have been fixed in a recent Qt5 release though, I t=
hink I saw a patch float past sometime in the the last year or so...<br><br=
></div><div>Of course, that doesn&#39;t help you right now :-)<br><br></div=
><div>John.<br><br></div></div></div></div>

--94eb2c08860607c8b105540fbeb3--

--===============4148595452807921702==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KUUdJUy1EZXZl
bG9wZXIgbWFpbGluZyBsaXN0ClFHSVMtRGV2ZWxvcGVyQGxpc3RzLm9zZ2VvLm9yZwpMaXN0IGlu
Zm86IGh0dHBzOi8vbGlzdHMub3NnZW8ub3JnL21haWxtYW4vbGlzdGluZm8vcWdpcy1kZXZlbG9w
ZXIKVW5zdWJzY3JpYmU6IGh0dHBzOi8vbGlzdHMub3NnZW8ub3JnL21haWxtYW4vbGlzdGluZm8v
cWdpcy1kZXZlbG9wZXI=

--===============4148595452807921702==--