Bug #27638 slow logging to CSV table inserts bad query_time and lock_time values

Description:
Log_to_csv_event_handler::log_slow() tries to store the number of seconds (for query_time or lock_time) directly in a TIME field via Field_time::store(longlong, bool).  However, that function expects a number in the format HHHMMSS, not a number of seconds.

How to repeat:
Noticed due to valgrind failure in count_distinct3 and multi_update tests, with slow log running.  Valgrind failure is a separate problem with pushing errors inside logging functions, not directly related to this bug.

Suggested fix:
Call calc_time_from_sec() and Field_time::store_time().

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/23761

ChangeSet@1.2559, 2007-04-04 11:11:18+02:00, tsmith@quadxeon.mysql.com +2 -0
  Bug #27638: slow logging to CSV table inserts bad query_time and lock_time values
  
  When MySQL logged slow query information to a CSV table, it stored the
  query_time and lock_time values with an incorrect formula.
  
  If the time was over 59 seconds, this caused incorrect statistics (either the
  slow query was not logged, or the time was far from correct).  This change
  fixes the method used to store those TIME values in the slow_log table.

Updated patch:
http://lists.mysql.com/commits/23817

(to->neg can't be cleared in calc_time_from_sec(), see for example Item_func_timediff::val_str())

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/23833

ChangeSet@1.2559, 2007-04-04 21:40:47+02:00, tsmith@quadxeon.mysql.com +6 -0
  Bug #27638: slow logging to CSV table inserts bad query_time and lock_time values
  
  When MySQL logged slow query information to a CSV table, it stored the
  query_time and lock_time values with an incorrect formula.
  
  If the time was over 59 seconds, this caused incorrect statistics (either the
  slow query was not logged, or the time was far from correct).  This change
  fixes the method used to store those TIME values in the slow_log table.

Pushed into 5.1.18-beta

Noted in 5.1.18 changelog.