Bug #27894 mysqlbinlog formats timestamp wrong in comment

Submitted: 17 Apr 2007 16:46 Modified: 29 Aug 2007 2:18
Reporter: Tobias Asplund Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S3 (Non-critical)
Version:5.1.17 OS:Linux
Assigned to: Chad MILLER CPU Architecture:Any
Tags: Contribution

[17 Apr 2007 16:46] Tobias Asplund 
Description:
mysqlbinlog formats datetime/timestamps wrong when outputting it.

Leading zeros are not displayed:
070406 => 746

Minor bug, but makes it a bit more tricky to read output.

does 7111 mean 1st november or 11th january?

How to repeat:
mysqlbinlog <binlog-file>
[17 Apr 2007 18:14] Jorge Bernal 
I think the problem might come from mysys/mf_iocache2.c:370:

      /* TODO: implement minimum width and precision */
[17 Apr 2007 18:32] Sveta Smirnova 
Thank you for the report.

Verified as described. Falcon tree is affected too.
[20 Apr 2007 12:37] Chad MILLER 
Received a contribution from Jorge Bernal Ordovás  <jbernal@warp.es>.
[23 Apr 2007 16:11] Chad MILLER 
http://lists.mysql.com/commits/25141
[23 Apr 2007 18:41] Rafal Somla 
Good to push.
[24 Apr 2007 0:55] Chad MILLER 
http://lists.mysql.com/commits/25201
[20 Aug 2007 10:20] Bugs System 
Pushed into 5.1.22-beta
[29 Aug 2007 2:18] Paul DuBois 
Noted in 5.1.22 changelog.

mysqlbinlog produced incorrectly formatted DATETIME and TIMESTAMP
values.
[31 Aug 2007 16:59] Paul DuBois 
This was pushed to 5.1.23, not 5.1.22.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.058 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.