Bug #62642 SQL history occasionally get's written into old files
Submitted: 6 Oct 2011 14:21 Modified: 22 Nov 2011 0:04
Reporter: Alex Whitman Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.35 CE OS:Windows (7)
Assigned to: CPU Architecture:Any
Tags: history, SQL

[6 Oct 2011 14:21] Alex Whitman 
Description:
While looking through some SQL history from months ago I noticed that some queries that I've run today have ended up being listed against a date in January.

Queries from today 06/10/2011 have been listed against 28/01/2011.  I've also noticed that some queries run on 08/09/2011 have been listed against 30/09/2010.

How to repeat:
Not sure how it happened, unable to reproduce but have noticed that it has (so far) happened twice.

Suggested fix:
Make sure queries are associated with the right date.
[18 Oct 2011 0:05] Alfredo Kojima 
Problem occurs when a history entry other than the last one is selected when the query is executed
[22 Nov 2011 0:04] Philip Olson 
Fixed as of 5.2.36:

+        A query history date would incorrectly change when a history
+        entry, other than the last one, was selected when the query was
+        executed.