Closed urugator closed 2 weeks ago
right, this is indeed an error, on first glance it must be a FieldType.DATETIME in place of FieldType.TIMESTAMP. I need to test that first with value range to confirm.
strange i don't reproduce this problem. What type of server+version are you using ?
Client: 3.3.0
Server:10.6.7-MariaDB
allright, reproduced
closing, since released in 3.3.1
Batch seems to treat all
Date
objects asTIMESTAMP
even though the actual column isDATETIME
/DATE
. The TIMESTAMP values are restricted to1970-01-01 00:00:01
-2038-01-19 03:14:07
/2106-02-07 06:28:15
, so if a date represented by the Date object is outside of this range, it's treated asnull
. If we attempt to insert the same date using string instead of Date object, everything works as expected.