View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000451||Database Workbench v6||SQL & Parameter Insight||public||2012-10-01 08:57||2022-01-26 10:47|
|Reporter||Doychin Bondzhev||Assigned To||Martijn Tonies|
|Summary||0000451: Option to enable/disable sql syntaxis hylighting in SQL Editor and max file size to automatically disable|
|Description||There should be an option to generally enable/disable syntax highlighting.|
Also it could be very handy to have an option to specify max file size for which by default highlighting is enabled. If SQL file is larger then this size highlighting to disable automatically. From there you can enable it for this file specifically.
This I suspect will make it much easier to work with large SQL files like MySql backups.
Good place to put these options as check box for example on the SQL Editor tool bar. Also if these options are going to increase maybe a drop down menu similar to one we have in Single SQL toolbar.
|Tags||No tags attached.|
Hmm, it seems slowness is more an issue of very very wide lines than of the number of lines.
Can you confirm?
I just suspected the problem comes from sql code analysis done by sql editor to properly highlight it.
The real problem could be in the fact that SQL editor needs lots of time to scroll each line but again this could be caused by the code analysis.
Just try to load big SQL file with lots of inserts and you will notice that when you try to scroll it does not really scroll but instead just moves the scroll bar position but screen is not repainted.
My real problem comes more from the fact that it takes ages to run script that is more then just a few hundred lines long. For scripts that represent database backups(MySQL) it could take ages to run and in most of the case it freezes at some point or is getting really slow.
In this case the real problem could be in the fact that you log each statement in the execution log and these controls are not very fast when they contain lots of lines ;-(
So if you can check where the actual bottleneck is this could pinpoint the real source of the problem which can be something else not the syntax highlight.
You can easily try yourself if it's the highlighting - open an editor without a connection: no highlighting.
With regard to script running, the output has a maximum number of lines, see Preferences, Editors, SQL/Script Editor.
OK but it is not only the output ;-)
It is the SQL editor him self that eats lots of CPU while executing SQL lines.
I think better is to look at issue 450. This will be much better to have and will avoid all the problems when running large SQL scripts from SQL Editor.
|Actually Scroll is really really fast when I load my test file in SQL Editor ;-) without highlighting.|
|2012-10-01 08:57||Doychin Bondzhev||New Issue|
|2012-10-01 10:35||Martijn Tonies||Status||new => acknowledged|
|2012-10-30 09:10||Martijn Tonies||Assigned To||=> Martijn Tonies|
|2012-10-30 09:10||Martijn Tonies||Status||acknowledged => assigned|
|2012-10-30 09:10||Martijn Tonies||Summary||Option to enable/disable sql syntaxis hylighting in SQL Editor => Option to enable/disable sql syntaxis hylighting in SQL Editor and max file size to automatically disable|
|2012-10-30 10:53||Martijn Tonies||Note Added: 0000143|
|2012-10-30 10:53||Martijn Tonies||Status||assigned => feedback|
|2012-11-06 11:20||Doychin Bondzhev||Note Added: 0000149|
|2012-11-06 11:20||Doychin Bondzhev||Status||feedback => assigned|
|2012-11-06 11:25||Martijn Tonies||Note Added: 0000150|
|2012-11-06 11:25||Martijn Tonies||Status||assigned => feedback|
|2012-11-06 11:27||Doychin Bondzhev||Note Added: 0000151|
|2012-11-06 11:27||Doychin Bondzhev||Status||feedback => assigned|
|2012-11-06 11:28||Doychin Bondzhev||Note Added: 0000152|
|2013-09-11 12:03||Martijn Tonies||Project||Database Workbench v4 => Database Workbench v5|
|2022-01-12 13:18||Martijn Tonies||Project||Database Workbench v5 => Database Workbench v6|
|2022-01-26 10:47||Martijn Tonies||Status||assigned => acknowledged|