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
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:
Desktop (please complete the following information):
Database