Habeeb556 commented on issue #31406: URL: https://github.com/apache/superset/issues/31406#issuecomment-3121975444
Hi @betodealmeida, I think I have identified the issue — it seems related to how **catalogs were introduced in `SIP-95`**. I am working with SQL Server (and sometimes Oracle), and when I run a query like: ```sql SELECT * FROM db.dbo.table ``` Superset interprets `db` as the **catalog**, not the **database**, which causes confusion. In `superset/security/manager.py`, the `get_schema_perm` method returns a `schema_perm` like: ``` [db].[db].[dbo] ``` This is incorrect in our case, as the first two parts are duplicates. I also noticed a comment in the code mentioning that: > "Because of this, the format used for permissions is different depending on whether a catalog is passed or not." This behavior may be a problematic for analytics teams, as they frequently use joins and need to reference the database explicitly by name. Could you please advise if there’s a recommended workaround or a potential fix for this? -- 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. To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
