xavier-GitHub76 opened a new issue, #35030: URL: https://github.com/apache/superset/issues/35030
### Bug description With Superset 4.1.1, when I change the source of a dataset, the list of schema is not correct. I created two databases with different numbers of schemas: <img width="385" height="167" alt="Image" src="https://github.com/user-attachments/assets/b8e6e413-7563-429d-8369-3dd5f829bcd7"; /> Both databases have schemas with identical names. The "test_schemas_2" database has two additional schemas. Within both databases, the "schema_a" schemas have the same table. Only the data value changes. I created two connections in Superset. I created a virtual dataset using: • the schema: test_schemas_1 • the table: schema_a <img width="278" height="321" alt="Image" src="https://github.com/user-attachments/assets/e272b21e-e63a-4837-ad6a-d174eb8f161b"; /> Finally, a diagram and dashboard were created Dashboard is OK : <img width="619" height="157" alt="Image" src="https://github.com/user-attachments/assets/49b2c25b-4df6-4fd3-963e-d12523970caf"; /> But if I change the source as following : <img width="399" height="497" alt="Image" src="https://github.com/user-attachments/assets/e2c889b1-884f-49f7-9fe6-15dfd9d4d439"; /> the diagram is in error : <img width="642" height="235" alt="Image" src="https://github.com/user-attachments/assets/d9f3d719-0f0c-4318-ae90-bd2a84a32bc8"; /> If I look at the list of proposed schemas for the source again, it is no longer consistent <img width="470" height="499" alt="Image" src="https://github.com/user-attachments/assets/f11294d2-010b-4529-85ce-7f2d9b5d8a65"; /> The last two schemas do not exist on "test_schemas_1"; they are only present on "test_schemas_2" You must force a refresh by changing the database to obtain the correct schemas. ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem. - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
