Bug #55237 Model Overview - Modified Column is incorrect
Submitted: 13 Jul 2010 22:20 Modified: 4 Jan 2011 16:22
Reporter: Jeremy Tinley Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.25 CE OS:Windows (7.0)
Assigned to: Alfredo Kojima CPU Architecture:Any

[13 Jul 2010 22:20] Jeremy Tinley
Description:
In the Model Overview, the Modified column is always set to current time when the model file is opened.

How to repeat:
Open an existing model file.
Look at the Model Overview, under Modified.
Observe that the timestamp should be the datetime that the file was opened.

Make a small change to a table. 
Observe that the timestamp for that one table is now newer.

Close the model file and reopen.

Observe that the timestamp for all files is now the datetime the file was opened again.

Suggested fix:
Do not update the timestamp of all tables when the file is opened.
[18 Nov 2010 20:52] Alfredo Kojima
fixed in repository
[8 Dec 2010 23:36] Johannes Taxacher
fix confirmed in repository
[4 Jan 2011 16:22] Tony Bedford
An entry has been added to the 5.2.31 changelog:

The Modified time displayed in the Model Overview was being incorrectly set to the current time.