dulajra commented on issue #24976: URL: https://github.com/apache/superset/issues/24976#issuecomment-2615230838
> Giving access to a schema is enough to grant the user implicit partial access to the database (on SQLLab), so no need to give the user wide access to the database itself. If the behaviour is like this then I agree with this statement. But it's not the case with superset (4.1.1). Even if the role has schema access but the database access is not specifically added for the role then you will get the following error when clicking on the table dropdown on SQL lab. ``` An error occurred while fetching table metadata. Please contact your administrator. ``` You will get the following error when running a SQL query on SQL lab. ``` can not access the query ``` The above errors will be gone if you grant database access for the role. But then you will see all the schemas on the schema dropdown irrespective of the schema access granted for the role. -- 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
