Error executing row count: duplicate column name
See original GitHub issueIf I execute the following query:
SELECT * FROM a
JOIN b ON b.foo = a.foo
And then click “Calculate total row count” below the result set, it says: Error executing row count
.
When checking out the error, it turns out that this is the generated query for the row count:
SELECT COUNT(*) FROM (SELECT * FROM a
JOIN b ON b.foo=a.foo
) dbvrcnt
Which results in the following error on server:
[1060] (conn:99533643) Duplicate column name 'foo'
Query is: SELECT COUNT(*) FROM (SELECT * FROM a
JOIN b ON b.foo=a.foo
) dbvrcnt
DBeaver 6.3.3 MariaDB server
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
SQL Duplicate column name error - Stack Overflow
is there an id column in the profiles table that is conflicting with another table's id column? You are selecting all columns, I...
Read more >SQL error messages and exceptions - Oracle Help Center
01503, The column <columnName> on table <tableName> has been modified by adding a not null ... 2201W, Invalid row count for FIRST/NEXT, must...
Read more >Resolve the error "HIVE_INVALID_METADATA” in Athena
This error happens when the AWS Glue table schema contains duplicate column names or columns with the same name as partition columns.
Read more >Duplicate Column Name causing issues in Copy Activity
once column names shows up then go back to Source Dataset and unselect "First Row as Header" and in Source Tab of Copy...
Read more >Why Am I Receiving a Duplicate Columns Error? - Fivetran
One column name uses camel case, one has a double underscore, and one has a single underscore. However, Fivetran normalizes all the column...
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
Wow you guys are fast. I can confirm that the issue is fixed in the latest git build. Thanks!!
verified