-
Notifications
You must be signed in to change notification settings - Fork 77
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
display improvements to %sqlcmd snippets
#648
Comments
If you have nothing in mind what I should work on next, I can start working on this. Acceptance Criteria
|
sure, please work on this |
@edublancas Let's say a user connects to connection A, creates a snippet under connection A, and then connects to another connection B. In this case, is the expected behavior of calling |
interesting point. right now, snippets are connection-independent so switching connections won't have any effect. they'll still show the same ones. But I like this Idea, we can work on it later. |
Sorry for not providing a clear explanation in my first question. @edublancas You are right about snippets being connection-independent. So there is no problem with getting a stored snippet from different connections. The problem occurs when I try to display a result of a snippet when the snippet uses a table that is not present in the current connection. The following code is a short demonstration. The full notebook is here After
After changing the connection with
Since the objective is to show a table and snippet when |
thanks for providing more feedback. I think let's keep it simple and allow users to run any snippets on any connection, it's on their side to ensure that whatever snippet they want to run is valid in the current connection |
we need to do some improvements when showing feedback to the user
for context: snippets.ipynb.zip
The text was updated successfully, but these errors were encountered: