You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I generated a new driver using the handy generator. Without any modification, I start the debug session, and in the new window that opened I try to add a new connection using the injected driver.
Unfortunately, the driver is missing from the list of installed drivers (I have Postgres driver installed from the Marketplace too, and that does show up).
However, after lots of trial and error, I managed to get it to show up. The trick is to set a brakpoint on the line api.registerPlugin(plugin); of extension.ts, and after opening the new connection menu, then resuming from said breakpoint, the new driver does appear in the list.
Further, it seems that the driver is loaded, as connections created using it "work" even if the driver is not listed in the new connection assistant.
Therefore it seems there might be some race condition when registering the generated driver skeleton.
Unfortunately, my knowledge of this extension is not sufficient to diagnose this tricky issue further.
To Reproduce
Steps to reproduce the behavior:
Generate driver with the generator
Open debug session
Try to create a new connection using generated driver in the assistant.
Driver is missing from the menu
Expected behavior
To see the driver in the list
Desktop (please complete the following information):
SQLTools Version: v0.22.10
VSCode Version: 1.46.1
Generator version: 0.1.4
OS: macOS 10.14.6
Driver:
PostgreSQL/Redshift
MySQL/MariaDB
MSSQL/Azure
SQLite
Other: generated unmodified driver scaffolding
The text was updated successfully, but these errors were encountered:
Describe the bug
I generated a new driver using the handy generator. Without any modification, I start the debug session, and in the new window that opened I try to add a new connection using the injected driver.
Unfortunately, the driver is missing from the list of installed drivers (I have Postgres driver installed from the Marketplace too, and that does show up).
However, after lots of trial and error, I managed to get it to show up. The trick is to set a brakpoint on the line
api.registerPlugin(plugin);
ofextension.ts
, and after opening the new connection menu, then resuming from said breakpoint, the new driver does appear in the list.Further, it seems that the driver is loaded, as connections created using it "work" even if the driver is not listed in the new connection assistant.
Therefore it seems there might be some race condition when registering the generated driver skeleton.
Unfortunately, my knowledge of this extension is not sufficient to diagnose this tricky issue further.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
To see the driver in the list
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: