Timestamp milliseconds wrongly interpreted if milliseconds start with zeros:

This issue occurred during Athena database testing (only 3 digits are supported for milliseconds). The timestamp type is recognised as 6 digits (but 3 digits set in the DB):
('endtime', DBAPITypeObject('TIMESTAMP'), 23, 23, 23, 6, 1)

• Millisecond values starting 0 are wrongly interpreted to 3 digit format:
  2020-01-05 11:02:14.080 -> 2020-01-05 11:02:14.800
• Millisecond values starting numeric value are interpreted to 6 digit format:
  2020-01-07 03:25:20.743 -> 2020-01-07 03:25:20.743000