Clickhouse auto completion doesn't work well
See original GitHub issueOn version 5.2.3.201810201753, when I write select * from, then I type first few letters (let’s say “def”), I get database auto completion list, with default
in list.
If I select default
with keyboard arrows or mouse i get default
def, so I have to delete def from the right side in order to continue.
The same is with field names. It used to work well in previous dbeaver versions.
I am connected to the Clickhouse database.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Broken command line suggestions · Issue #21829 - GitHub
Describe the bug Command line suggestions don't work in the latest client ... Check table existence for clickhouse client autocompletion
Read more >Troubleshooting | ClickHouse Docs
If you do not see an error at the end of the file, look through the entire file starting from the string: <Information>...
Read more >Settings | ClickHouse Docs
Forces a query to an out-of-date replica if updated data is not available. See Replication. ClickHouse selects the most relevant from the outdated...
Read more >SELECT Query | ClickHouse Docs
Code : 42. DB::Exception: Received from localhost:9000. DB::Exception: Number of arguments for function plus does not match: passed 3, should be 2.
Read more >CREATE VIEW | ClickHouse Docs
Query result as well as partial result needed to combine with new data are ... Live view will not work for queries that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This was already reported and 5.2.3 re-released. You need to visit dbeaver.io and download and install 5.2.3 again!
@ghuname This particular issue was fixed in the very same day of 5.2.3 release. Making two releases in the same day is a bit strange. So we decided to make a hotfix build. But I agree that we need some special procedure for such cases.