Bug #87088 Write connection ID to sql_history file
Submitted: 17 Jul 2017 0:30 Modified: 1 Feb 2018 10:41
Reporter: Stuart Uren Email Updates:
Status: Verified Impact on me:
Category:MySQL Workbench Severity:S4 (Feature request)
Version:6.3.9, 6.3.10 OS:Any
Assigned to: CPU Architecture:Any
Tags: sql_history

[17 Jul 2017 0:30] Stuart Uren
Your doing a wonderful job with SQL Workbench.

A new request please around SQL logging:

Can we please have the file written to the sql_history directory to contain a connection ID?    At the moment, all the commands run from Workbench go into the single file, but there is no way to tell which connection they were run under. 



How to repeat:
browse C:\Users\xxxx\AppData\Roaming\MySQL\Workbench\sql_history.  
files are per day - i.e. 2017-07-12, but looking at the file contents, there is no way to distinguish which connection/environment they ran under.

Suggested fix:
add a connection ID to the file.
[17 Jul 2017 0:30] Stuart Uren
updated synopsis
[1 Feb 2018 10:41] MySQL Verification Team
Hello Stuart Uren,

Thank you for the feature request!