MySQL Bugs: #98112: File locking on Widows 10

Bug #98112	File locking on Widows 10
Submitted:	3 Jan 2020 0:18	Modified:	3 Feb 2020 11:40
Reporter:	Curtis DeHart	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	8.0.18	OS:	Windows (Microsoft Windows 10 Pro)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	WBBugReporter

Description:
After dragging a .sql file from a Windows directory into the workbench, running the script, and closing the tab the file is locked. The only way to release the file lock is to close workbench all the way. Disconnecting from the instance does not work.

How to repeat:
Drag .sql file from directory onto Workbench (with an active connection), run script, close tab with script in it, try to delete or move source script in Windows explorer with Workbench still open.

Suggested fix:
Read .sql file and release handle on it or release lock on file when tab containing script is closed out.

Hello Curtis DeHart,

Thank you for the report.
I tried to reproduce your issue on windows 10 with workbench 8.0.18 using dummy .sql file but I am not seeing any issues at my end. To investigate further this issue at our end, may I kindly request you to provide a sample .sql file, unaltered WB log file with debug mode enabled, details on whether .sql file was already open elsewhere(any other editor etc). Thank you.

Regards,
Ashwini Patil

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".