Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance, compile delay, persistent sqlplus / sqlcl connection #38

Open
yevon opened this issue Oct 10, 2020 · 4 comments
Open

Performance, compile delay, persistent sqlplus / sqlcl connection #38

yevon opened this issue Oct 10, 2020 · 4 comments

Comments

@yevon
Copy link
Collaborator

yevon commented Oct 10, 2020

Hi @mickeypearce,

I've noticed that every time that a package or something gets compiled, a new sqlplus session is established, then compiles, and then terminates. This is quite slow as you have to wait for sqlplus initialisation every time. Would it be possible to keep a persistent connection for sqlplus waiting for new compile commands? This way the session would be always active after first compile attempt with no waiting. The idea is keeping an active session for every schema simultaneously every time that you perform a compile command, and following compile commands would execute in the same session with no waiting.

I just came across with this nice extension for vscode and I've been trying it, because I want to leave using sqldeveloper as IDE as it is very basic and a nightmare of bugs, hangs, slow etc. I have some ideas to improve it and I would love help developing it if you need help, as I think that it is near perfect for our needs.

@mickeypearce
Copy link
Owner

Hey @yevon ,
I am not sure about a persistent sqlcl connection but I kindly invite you to contribute, you can open a PR I will gladly review it and provide with assistance in case you will need some help.

@yevon
Copy link
Collaborator Author

yevon commented Oct 11, 2020

I tried to clone this repository and set up node dependencies with no success, I'm out this week so I cannot give you more detail rightnow. Do you have some quick initial guide with dependencies for being able to debug and develop the extension? Or shoud I use the oradew vscode docker environment?

@mickeypearce
Copy link
Owner

npm install should do the trick with with dependencies. Then you can just launch extension (F5).

@yevon
Copy link
Collaborator Author

yevon commented Oct 18, 2020

The problem was node version, I had version 14 installed and I didn't check that max allowed is 12.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants