[GH-ISSUE #528] Query returns nothing when column names not defined #158

New issue

Closed

opened 2026-03-07 20:45:31 +03:00 by kerem · 4 comments

kerem commented

2026-03-07 20:45:31 +03:00

Owner

Originally created by @RoryMMMM on GitHub (Nov 3, 2021).
Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/528

Describe the bug
When doing a query that has ambiguous named columns (like an aggregation) the cloudbeaver query window returns nothing. The same query will return data when run in some other tool (tested with pymssql lib).

To Reproduce
Steps to reproduce the behavior:

Running the query "SELECT * FROM my_table WHERE id=1" returns data in both cloudbeaver and pymssql
Running the query "SELECT count(*) FROM my_table WHERE id=1" returns data with pymssql. In cloudbeaver an empty result window is returned. There doesn't seem to be a warning and the query takes a reasonable amount of time, which leads me to believe it gets executed.
Running the query "SELECT count(*) AS 'count' FROM my_table WHERE id=1" returns data with pymssql and cloudbeaver.
The query "SELECT 'some_string_constant', * FROM my_table" causes the same odd behaviour.
The query "SELECT 'some_string_constant' as 'str_cnst', * FROM my_table" fixes the same odd behaviour.

Desktop (please complete the following information):

OS: Service running on ubuntu 21.04, in a docker container, query is run from a Win10 machine via
Browser: Chrome 95.0.4638.54 (Official Build) (64-bit)
Version: Docker image dbeaver/cloudbeaver:21.2.0

Database

The DB being queried is a MS SQL Server Microsoft SQL Server 2017 (RTM-GDR) (KB4583456) - 14.0.2037.2 (X64)

Originally created by @RoryMMMM on GitHub (Nov 3, 2021). Original GitHub issue: https://github.com/dbeaver/cloudbeaver/issues/528 **Describe the bug** When doing a query that has ambiguous named columns (like an aggregation) the cloudbeaver query window returns nothing. The same query will return data when run in some other tool (tested with pymssql lib). **To Reproduce** Steps to reproduce the behavior: * Running the query "SELECT * FROM my_table WHERE id=1" returns data in both cloudbeaver and pymssql * Running the query "SELECT count(*) FROM my_table WHERE id=1" returns data with pymssql. In cloudbeaver an empty result window is returned. There doesn't seem to be a warning and the query takes a reasonable amount of time, which leads me to believe it gets executed. * Running the query "SELECT count(*) AS 'count' FROM my_table WHERE id=1" returns data with pymssql and cloudbeaver. * The query "SELECT 'some_string_constant', * FROM my_table" causes the same odd behaviour. * The query "SELECT 'some_string_constant' as 'str_cnst', * FROM my_table" fixes the same odd behaviour. **Desktop (please complete the following information):** - OS: Service running on ubuntu 21.04, in a docker container, query is run from a Win10 machine via - Browser: Chrome 95.0.4638.54 (Official Build) (64-bit) - Version: Docker image dbeaver/cloudbeaver:21.2.0 **Database** - The DB being queried is a MS SQL Server Microsoft SQL Server 2017 (RTM-GDR) (KB4583456) - 14.0.2037.2 (X64)

kerem

2026-03-07 20:45:31 +03:00

closed this issue
added the
xf:sql editor

x:sql server
labels

kerem commented

2026-03-07 20:45:32 +03:00

Author

Owner

@kseniiaguzeeva commented on GitHub (Nov 3, 2021):

Could you please tell what database do you use?

@kseniiaguzeeva commented on GitHub (Nov 3, 2021): Could you please tell what database do you use?

kerem commented

2026-03-07 20:45:32 +03:00

Author

Owner

@RoryMMMM commented on GitHub (Nov 3, 2021):

Added DB version to top page

@RoryMMMM commented on GitHub (Nov 3, 2021): Added DB version to top page

kerem commented

2026-03-07 20:45:32 +03:00

Author

Owner

@kseniiaguzeeva commented on GitHub (Nov 3, 2021):

Thank you for the report. Reproduced.

@kseniiaguzeeva commented on GitHub (Nov 3, 2021): Thank you for the report. Reproduced. ![chrome_nlO3tPanGr](https://user-images.githubusercontent.com/51405061/140048294-deec8039-1158-4b96-b7a7-937d8a14bd4c.png)

kerem commented

2026-03-07 20:45:32 +03:00

Author

Owner

@kseniiaguzeeva commented on GitHub (Nov 24, 2021):

The issue is fixed in the latest 21.2.3 release.

@kseniiaguzeeva commented on GitHub (Nov 24, 2021): The issue is fixed in the latest 21.2.3 release.