Any possible milestone?

This is relatively big feature.
There are too many different questions and possibly too many UI additions. I can't say when we'll have resources for that. Maybe we more people would vote for this feature.

Sorry, I was not trying to prioritize the ticket, but just commenting to make sure it was not forgotten.
Thank you for the wonderful application and thank you for keeping it free.

This is relatively big feature.

I found it by way of the good first issue label. Would you please clarify whether you think it is a good first issue?

A suggestion: I suppose it might be quite easy to implement this as a command line parameter. Just like now you allow to execute tasks (which are very similar in nature to a sql script).
Of course running tasks from the command line is a EE feature, so if a similar implementation is chosen, there goes the "thank you for keeping it free" 😃.

I am only asking to provide a right click file within dbeaver ide and run script, without opening the sql script editing window. I don't think it will clash with EE version.
Clarifying: I am not asking for commandline args, I am only asking a right click within the Dbeaver IDE.

This is especially useful when working with database dumps, which are usually large in size. If I want to import a db dump in dbeaver I would usually have to wait around 4 to 5 minutes for the editor to load after opening the sql file, only to then wait 4 to 5 minutes more after switching the database on which I would want to import this dump.

Hello, I just tried to make this feature by myself. But I got caught in a cyclic dependency problem.

Following is a sequence of my approach:
(1) Make 'Run Script' menu and command in 'org.jkiss.dbeaver.ui.navigator'
(2) Write handler setting in plugin.xml to connect the command with 'SQLEditorHandlerExecute' class in 'org.jkiss.dbeaver.ui.editor.sql'
(3) Add 'org.jkiss.dbeaver.ui.editor.sql' in Required-Bundle of MANIFEST
(4) Because 'org.jkiss.dbeaver.ui.editor.sql' already has dependency on 'org.jkiss.dbeaver.ui.navigator', (3) raises cyclic dependency and compile fails

I tried to find a way to execute SQL without 'SQLEditorHandlerExecute' class, but I couldn't make it. Could anyone have better approach to make this feature? Any advice would be appreciated!

Hello, I just tried to make this feature by myself. But I got caught in a cyclic dependency problem.

Following is a sequence of my approach: (1) Make 'Run Script' menu and command in 'org.jkiss.dbeaver.ui.navigator' (2) Write handler setting in plugin.xml to connect the command with 'SQLEditorHandlerExecute' class in 'org.jkiss.dbeaver.ui.editor.sql' (3) Add 'org.jkiss.dbeaver.ui.editor.sql' in Required-Bundle of MANIFEST (4) Because 'org.jkiss.dbeaver.ui.editor.sql' already has dependency on 'org.jkiss.dbeaver.ui.navigator', (3) raises cyclic dependency and compile fails

I tried to find a way to execute SQL without 'SQLEditorHandlerExecute' class, but I couldn't make it. Could anyone have better approach to make this feature? Any advice would be appreciated!

Hi. As i am new to Open Source in general i dont know if this will be Helpful and i do not know if you are still interest in solving this Issue. But i have used Lazy Dependencies in the Past for handling necessary cyclic dependencies. So you only Get the dependency once required.
The way i know this in C# is we inject the ServiceProvider[Or equivalent Factory - whatever is used for getting the depency into our class in a clean way, without directly injecting it]
We then make a private member for the dependency, which is nullable and null on intiation of the class
Then we write a getter that intiates the dependency member if null and then returns it either way. This Getter is what we use then to access our dependency.
This way we are not injecting cyclicly on object creation. We are just left with a bidirectional dependancy.
I would apreciate it if one of the big boys of this repository would tell me if this kind of action is ok and how good of an idea it seems.
As, if @CodyBuilder-dev is not interested in pursuing this issue further i would like to tackle it as my first issue.