Skip to content
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

Error on case-sensitive names for table/fields/etc. in PostgreSQL #3001

Closed
3 tasks done
Srynetix opened this issue Jun 20, 2017 · 2 comments
Closed
3 tasks done

Error on case-sensitive names for table/fields/etc. in PostgreSQL #3001

Srynetix opened this issue Jun 20, 2017 · 2 comments

Comments

@Srynetix
Copy link

Hello all !

I am currently running Superset 0.18.4 on Docker, connecting with a PostgreSQL database linked to a Django project, containing table names and fields with capital letters.
When executing SQL queries outside of Superset, we have to double-quote each table name with the corresponding schema and each field containing capital letters.

The problem is that PostgreSQL will lowercase every names if they are not double-quoted.
So, when exploring data and when using SQL Lab, there are errors like 'relation "my_table" does not exist'.

  • I have checked the superset logs for python stacktraces and included it here as text if 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 (except for capital letter in varnames of a postgres table #408 one year ago)

Superset version

0.18.4 (installed via pip)

Expected results

Working SQL queries even with case-sensitive table and field names.

Actual results

Errors because of automatic lower-case.

Steps to reproduce

Try to execute queries against a table and fields with capital letters in a PostgreSQL database.

@xrmx
Copy link
Contributor

xrmx commented Jun 20, 2017

Please if you found the same bug no need to open a new one, just subscribe to the other one. If you have more information than the one already reported just update it.

@mistercrunch
Copy link
Member

Notice: this issue has been closed because it has been inactive for 307 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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants