Bug #57878 WorkBench session handling
Submitted: 1 Nov 2010 2:53 Modified: 4 Nov 2010 18:02
Reporter: Roel Van de Paar Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.29 OS:Any
Assigned to: CPU Architecture:Any

[1 Nov 2010 2:53] Roel Van de Paar
Description:
Open 2x WB and open the same (existing) EER model in both sessions. Result:

-------------------------------------
Document Recovery
-------------------------------------
The document D:\WorkBench Bugs\EERs\Work copies\test7.mwb was not properly closed in a previous session on 2010-11-01 13:36.
The file you're about to open was last saved .
Would you like to open its recovered contents or continue opening the selected file and clean up the autosave data? 
-------------------------------------
[Recover] [Continue]
-------------------------------------

It is also not possible to cancel here.

How to repeat:
As per the above.

Suggested fix:
Instead, this should give something like:

-------------------------------------
File open elsewhere or file was not closed properly during a previous session.
-------------------------------------
We detected an issue with the document D:\WorkBench Bugs\EERs\Work copies\test7.mwb. 

This may be because you have this file open elsewhere in another WorkBench session, or because you failed to properly close it in a previous session. 

This file was last saved on 2010-11-01 10:00AM, and the last session date/time attached to this document was 2010-11-01 01:36PM.

Would you like to open its recovered contents (select [recover]) or continue opening the selected file and clean up the autosave data (select [continue]) or cancel? 
-------------------------------------
[Recover] [Continue] [Cancel]
-------------------------------------

(Also note the change to AM/PM time since 11:00 may mean 11:00AM or 11:00PM)

Even better would be to only give one cause ("File open elsewhere" or "file was not closed properly during a previous session.") - if this can be checked for.

Please also clarify further what the implications and differences are in regards/between Recover <> Continue/Autosave.
[4 Nov 2010 18:02] Johannes Taxacher
setting this bug as a duplicate of Bug #56067 because the fix/solution will also get rid of this reports problem.