harshgadhia opened a new issue #17104: URL: https://github.com/apache/superset/issues/17104
### Steps to reproduce: 1. Go to SuperSet -> SQL Lab -> SQL Editor 3. Choose Database `examples` (default postgres provided out-of-box as example) -> schema: `information_schema` 4. In the editor, run a query like: `select * from collations` ### Expected results The database selection done on the left side is should be persisted in the query tab, and one can run a query without using fully qualified database name. That is, when a query like `select * from collations` is run, it should be translated to `select * from information_schema.collations` automatically, this is respecting the schema selections done on the left. ### Actual results #### Positive scenario Works when using fully qualified table / relation name:  #### Error Scenario: However, The database returns an error, complaining that the table / relation does not exists when not using fully qualified name. #### Screenshots Error Screenshot:  ### Environment - browser type and version: Google Chrome Version 94.0.4606.81 (Official Build) (x86_64) - superset version: `superset version` - python version: `python --version` 3.8.12 - node.js version: `node -v` 16 - any feature flags active: NO ### Checklist Make sure to follow these steps before submitting your issue - thank you! - [x] I have reproduced the issue with at least the latest released version of superset. - [x] I have checked the issue tracker for the same issue and I haven't found one similar. -- 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]
