aniruddhaparte opened a new issue, #24602: URL: https://github.com/apache/superset/issues/24602
Description: When editing a database connection in Superset's Advanced Section, the settings get cached and persist when opening subsequent database connections. This behavior causes the same settings applied to a previous database connection to be displayed when editing a new connection. #### How to reproduce the bug 1. Open Superset and navigate to the Database Connection settings. 2. Edit an existing database connection in the Advanced Section. 3. Modify the connection settings, such as the host, port, username, or password. 4. Save the changes and close the connection settings. 5. Open a different database connection in the Advanced Section. 6. Notice that the settings from the previous connection are displayed instead of the default or previously saved settings for the current connection. ### Expected results When editing a new database connection, the Advanced Section should display the default or previously saved settings specific to that connection. The settings from previous connections should not be cached or carried over to new connections. ### Actual results The Advanced Section in the Database Connection settings displays the same settings as the previous connection, leading to confusion and potential misconfiguration. #### Screenshots This image shows the settings for one DB connection "Shillelagh"  But when i open another databases connection it shows the same Settings for the an other db:  ### Environment (please complete the following information): - browser type and version: Google Chrome 114.0.5735.133 - superset version: `2.1.0` - python version: `Python 3.8.16` - node.js version: `node -v` - any feature flags active: "ALERT_REPORTS": True, "DASHBOARD_CROSS_FILTERS": True, "DASHBOARD_RBAC": True, "GENERIC_CHART_AXES": True, "ALLOW_FULL_CSV_EXPORT": True, "DRILL_TO_DETAIL": True, "HORIZONTAL_FILTER_BAR": True ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [ ] I have checked the superset logs for python stack traces and included it here as text if there are any. - [ ] I have reproduced the issue with at least the latest released version of superset. - [ ] I have checked the issue tracker for the same issue and I haven't found one similar. ### Additional context -- 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]
