-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQL Lab - schema selection on the left side leads to "(psycopg2.OperationalError) FATAL: database "schema" does not exist" on postgres #1558
Comments
Reproduced on 0.13.2 via: https://github.com/amancevice/superset Full redacted stacktrace:
Yes, with the duplication. |
0.14.1 same |
3 tasks
Notice: this issue has been closed because it has been inactive for 504 days. Feel free to comment and request for this issue to be reopened. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scenario:
If I use the SQL Lab with a postgres database, that has multiple schemas, the schema selection on the left side leads to (psycopg2.OperationalError) FATAL: database "schema" does not exist.
Even though the inspection of the schema works and I get all tables under the third dropdown.
However if I leave the schema dropdown on the left empty and write a query like this:
SELECT *
FROM schema.test LIMIT 100
it works.
I guess the schema selection is misinterpreted in some way...
Make sure these boxes are checked before submitting your issue - thank you!
Caravel version
0.12.0
Expected results
SELECT *
FROM schema.testtable LIMIT 100 succeeds
with the selected schema on the left side.
Actual results
SELECT *
FROM schema1.testtable LIMIT 100
leads to
(psycopg2.OperationalError) FATAL: database "schema1" does not exist
Steps to reproduce
SELECT *
FROM schema1.testtable LIMIT 100
The text was updated successfully, but these errors were encountered: