-
Notifications
You must be signed in to change notification settings - Fork 50
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
DBeaver can not select schema #261
Comments
Works as expected using the default MySQL driver. Doesn't seem to be a setting at fault from what I can see |
Hello @tomchiverton Thank you for raising the issue. We understand this issue is causing inconveniences in your workflows. We'll be investigating this issue and will update you when we have a release. We appreciate your patience. |
Hello @tomchiverton According to DBeaver documentation, you can specify custom queries for a driver to facilitate some UI features like changing current schema. You can configure them at
I hope this solution solve the issue! |
Yup, pull for updating the docs on it's way. |
Describe the bug
Unable to choose an available schema once connected
Expected Behavior
Drop down closes, selecting the correct schema
Current Behavior
Drop down closes, but value in tool bar remains "N/A"
Queries entered need to fully specify the schema.tablename or use "use schema".
Reproduction Steps
Set up new driver as per the README (separate MR opened to correct the URL template ; #260)
Create new connection using new driver
Open the new connection as SQL Console
Pick a schema from the drop down list in toolbar, next to where it lists the connection name
Possible Solution
No response
Additional Information/Context
DBeaver 22.1.5
The AWS JDBC Driver for MySQL version used
1.1.0
JDK version used
openjdk 11.0.12 2021-07-20
Operating System and version
Ubuntu 20.04 LTS
The text was updated successfully, but these errors were encountered: