[GitHub] [incubator-superset] CrashLaker opened a new issue #7316: Help understanding superset complaining about columns used in subquery

[GitBox <gi...@apache.org>]

CrashLaker opened a new issue #7316: Help understanding superset complaining about columns used in subquery
URL: https://github.com/apache/incubator-superset/issues/7316
 
 
   Hi all.
   
   I'm trying to understand why a query that runs fine in Microsoft SQL Server Management Studio isn't working in superset. 
   
   So my database is Microsoft SQL Server and for the connector I'm using pymssql.
   ```python3
   # pymssql
   engine = create_engine('mssql+pymssql://scott:tiger@hostname:port/dbname')
   ```
   I'm also using superset release 0.31.0rc18 + the other components specified in docker-compose.yml config based on that commit.
   
   The query I'm trying to run is somewhat like this:
   ```sql
   select * from a 
   join(subquery) b
   on a.col = b.col
   where blabla
   ```
   
   The above command returns me the following error:
   `(8156, b"The column 'xxxx' was specified multiple times for 'inner_qry'.DB-Lib error message 20018, severity 16:\nGeneral SQL Server error: Check messages from the SQL Server\n")`
   
   The solution I found was to manually specify which columns I wanna see like:
   ```sql
   select a.col1,a.col2,a.col3... from a 
   join(subquery) b
   on a.col = b.col
   where blabla
   ```

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org