mirror of
https://github.com/dbeaver/cloudbeaver.git
synced 2026-03-04 08:52:27 -05:00
Database Not Selected Error Despite Database Being Chosen #774
Labels
No labels
AS
can't reproduce
can't reproduce
deployment
development
documentation
duplicate
duplicate
ee
enhancement
external
new driver
performance
third party issue
wait for response
wait for review
wontfix
x:Oracle
x:cassandra
x:clickhouse
x:db2
x:duckdb
x:greenplum
x:h2
x:h2gis
x:hana
x:hive
x:intersystems
x:kyuubi
x:maria
x:mongo
x:mysql
x:postgresql
x:presto
x:sql server
x:sqlite
x:teradata
x:trino
xf:accessibility
xf:administration
xf:authentication
xf:aws
xf:commit-mode
xf:connection
xf:data editor
xf:datatransfer
xf:dba
xf:driver management
xf:erd
xf:filters
xf:i18n
xf:i18n
xf:installer
xf:json
xf:ldap
xf:local config
xf:log viewer
xf:metadata
xf:metadata editor
xf:navigator
xf:okta
xf:query manager
xf:resource manager
xf:scripts
xf:sql editor
xf:tasks
xf:ui/uix
xo: Firefox
xo:eclipse
xo:internet explorer
xo:macos
xp:major
xrn:internal
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/cloudbeaver#774
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @matthieukhl on GitHub (Aug 22, 2024).
Context
Our team is encountering an issue where Cloudbeaver does not recognize that a database has been selected, leading to an error that suggests no database is chosen.
The query fails as if no database has been selected, even though the user explicitly chooses a database beforehand (see screenshot below).
This issue occurs intermittently when using the MySQL connector with TiDB.
Restarting the Docker container hosting Cloudbeaver temporarily resolves the issue, but it eventually reoccurs. The database is correctly selected within the UI, yet queries fail with an error stating that no database has been selected.
Steps to reproduce
Logs
Log Snippet When Bug Occurs (After Running a SELECT Query) BEFORE Docker Restart
Log Snippet When Running the USE Query BEFORE Docker Restart
Log Snippet AFTER Restarting Docker
Log Snippet After Running the Same SELECT Query AFTER Docker Restart
Additional Information
We are using the Community Edition of Cloudbeaver with the MySQL connector to connect to our TiDB Cluster.
We are currently running Cloudbeaver 24.1.3 and will update to Cloudbeaver 24.1.5.
Most of our team is using Cloudbeaver on Google Chrome.
Could you please investigate this issue? Thank you.
@EvgeniaBzzz commented on GitHub (Aug 23, 2024):
Hi @matthieukhl
Please try updating your version to 24.1.5 and see if the problem persists.
There may still be consequences from this issue
@matthieukhl commented on GitHub (Aug 24, 2024):
Hi
Thanks for your quick reply. I have updated CloudBeaver to v24.1.5 and will monitor this issue.
I will update this issue in about a week or so to inform you if the described behaviour happened again or not.
@matthieukhl commented on GitHub (Aug 26, 2024):
Hi,
I've reproduced the bug today on Cloudbeaver Community Edition v24.1.5.
Here are the logs when I execute a "USE database" query:
Here are the logs when I execute a SELECT query:
Note: if I specify the database in the SELECT query it does run the query correctly
@LonwoLonwo commented on GitHub (Aug 26, 2024):
Hello.
Please let me know if I am wrong.
Are you trying to use the USE database query instead of the change-default-database-dropdown? Because it doesn't work in CloudBeaver, only in DBeaver. It would be best to use the dropdown to change your default database. Or use the full table name, yes.
@matthieukhl commented on GitHub (Aug 26, 2024):
Hi @LonwoLonwo,
Thanks for taking some time to check in on that issue.
I have been able to effectively execute a
USE databasestatement and then query my database without specifying thedatabase.table_namebut onlytable_nameby the past on Cloudbeaver.Either way, in this particular issue, even selecting the database, or container as it says, in the dropdown menu, it still produces the error.
@LonwoLonwo commented on GitHub (Aug 30, 2024):
Maybe this case is connected with https://github.com/dbeaver/dbeaver/issues/35040
Waiting for the fix from DBeaver-side. Will see in the 24.2.0 release.
@LonwoLonwo commented on GitHub (Sep 2, 2024):
Please check the latest release 24.2.0.
The catalog changing behavior may be correct now.
@matthieukhl commented on GitHub (Sep 3, 2024):
Hi @LonwoLonwo will upgrade to 24.2.0 next week and update this thread. Thanks for your time and for your work, Cloudbeaver is greatly appreciated by our teams :)
@EvgeniaBzzz commented on GitHub (Oct 18, 2024):
Hi @matthieukhl
Any news here?
@matthieukhl commented on GitHub (Oct 24, 2024):
Hi @EvgeniaBzzz sorry for the late response.
I've asked around the teams, they are still reporting the issue but I haven't had time to investigate the logs. Will share some news as soon as possible.
@matthieukhl commented on GitHub (Nov 5, 2024):
Hi @EvgeniaBzzz
The issue just happened again. Below you'll find logs I've extracted while the issue was happening:
@EvgeniaBzzz commented on GitHub (Nov 5, 2024):
I see 😞
We need some extra time to investigate your issue
@DenisSinelnikov commented on GitHub (Nov 13, 2024):
Hi @matthieukhl,
I am trying to figure out your problem, but I have not been able to reproduce it. I would like to clarify the following things:
@matthieukhl commented on GitHub (Nov 14, 2024):
Hi @DenisSinelnikov thanks for taking some time to look into this issue.
I hope this satisfies your questions :)