Bug #6989 Timestamp does not include milliseconds
Submitted: 3 Dec 2004 13:58 Modified: 14 Feb 2006 13:24
Reporter: Paul Fallon Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Data Types Severity:S4 (Feature request)
Version:4.1.7 OS:Windows (Win 2000/XP)
Assigned to: CPU Architecture:Any

[3 Dec 2004 13:58] Paul Fallon 
Description:
Java includes milliseconds in its timestamp, but when saved to a InnoDB record, the milliseconds is removed.
A timestamp with an increment of 1 second is not possible for us to use as a timestamp as we need it to be unique, but without milliseconds this is not possible.

email: paul.fallon@seb.se

How to repeat:
Attempt to save a field of type timestamp, with data including milliseconds. 

Suggested fix:
Include milliseconds in timestamp:
ex: 2004-12-03 12:01:01:01
[3 Dec 2004 18:01] Heikki Tuuri 
Hi!

The timestamp is taken by MySQL, and only stored inside the InnoDB storage engine. I am changing this to a general MySQL feature request.

Thank you,

Heikki
[14 Feb 2006 13:24] Valeriy Kravchuk 
Thank you for a reasonable feature request.