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

MySQL Execute in new connection at query tab #236

Closed
SmileYzn opened this issue Apr 18, 2022 · 2 comments
Closed

MySQL Execute in new connection at query tab #236

SmileYzn opened this issue Apr 18, 2022 · 2 comments
Assignees
Labels
bug 🪲 Something isn't working

Comments

@SmileYzn
Copy link
Contributor

Describe the bug
When you execute a query in query tab, click on disconnect button at top.
And back to a new connection, the select field is blank but query instead of send to new connection, still sending to old disconnected server.

Expected behavior
Execute query in correct connection, or just trhow a error forcing user to select a correct database in db field

Screenshots
cinnamon-20220418-1.webm.tar.gz

Application (please complete the following information):

  • Client Maria DB
  • Version 10.3.27
  • Distribution: Linux

Desktop (please complete the following information):

  • OS: Linux Mint 20.3
  • Version Linux Mint 20.3

Additional context
The attached file is a webm video

@Fabio286 Fabio286 added the bug 🪲 Something isn't working label Apr 18, 2022
@Fabio286
Copy link
Member

Hi Cleverson,

thanks for this report and the attached video!
The bug occurs because query tabs gets as target schema the selected one in left bar when you open a new one.
In your case the schema remains cached on the tab, but shouldn't if not available directly on explore bar on left.
As i can see from the video its not visible on schema select, on those cases cached schema should be cleared.
Antares uses the new connection, but targets previous schema.
If you target the right schema from following select everything should work fine.

image

I will fix this on next release, thanks again for your time.

@SmileYzn
Copy link
Contributor Author

Yes it is working here in this way.

I did not have sure where is needed to do in this case, i think only get a error message when run query.
Since is sending commands to old selected schema

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 🪲 Something isn't working
Projects
Status: Done
Development

No branches or pull requests

2 participants