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
Hello! I’ve been working on an extension for Azure Data Studio that allows users to specify connections for code cells in SQL notebooks. The goal is to enable querying multiple databases within a single notebook. I’ve made significant progress, but there’s one crucial piece missing.
I’ve noticed that while you can change the kernel, there’s currently no direct way to switch the connection within the same notebook. Currently, I map code cells to connections based on user selections in a wizard. However, without the ability to change the connection dynamically, the solution won’t be complete.
I’m wondering if we’re allowed to contribute to the API for this functionality. After posting this, I’ll look into the guidelines. If everything aligns, I’d be more than happy to take a stab at contributing this as a full feature for ADS as well. Thank you for your time and consideration!
The text was updated successfully, but these errors were encountered:
Hello! I’ve been working on an extension for Azure Data Studio that allows users to specify connections for code cells in SQL notebooks. The goal is to enable querying multiple databases within a single notebook. I’ve made significant progress, but there’s one crucial piece missing.
I’ve noticed that while you can change the kernel, there’s currently no direct way to switch the connection within the same notebook. Currently, I map code cells to connections based on user selections in a wizard. However, without the ability to change the connection dynamically, the solution won’t be complete.
I’m wondering if we’re allowed to contribute to the API for this functionality. After posting this, I’ll look into the guidelines. If everything aligns, I’d be more than happy to take a stab at contributing this as a full feature for ADS as well. Thank you for your time and consideration!
The text was updated successfully, but these errors were encountered: