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

Postgres timestamp with timezone causes error #20450

Closed
3 tasks done
dheardal opened this issue Jun 21, 2022 · 1 comment
Closed
3 tasks done

Postgres timestamp with timezone causes error #20450

dheardal opened this issue Jun 21, 2022 · 1 comment
Labels
#bug Bug report

Comments

@dheardal
Copy link

dheardal commented Jun 21, 2022

A clear and concise description of what the bug is.

How to reproduce the bug

  1. Setup a postgres table with a timestamp with time zone (timstamptz) column
  2. Query that column using sql editor or consume that column in a chart
  3. See error

Expected results

Be able to see the column

Actual results

superset_1        | Traceback (most recent call last):
superset_1        |   File "/app/superset/views/base.py", line 211, in wraps
superset_1        |     return f(self, *args, **kwargs)
superset_1        |   File "/app/superset/utils/log.py", line 245, in wrapper
superset_1        |     value = f(*args, **kwargs)
superset_1        |   File "/app/superset/views/core.py", line 2574, in sql_json
superset_1        |     command_result: CommandResult = command.run()
superset_1        |   File "/app/superset/sqllab/command.py", line 104, in run
superset_1        |     raise ex
superset_1        |   File "/app/superset/sqllab/command.py", line 96, in run
superset_1        |     status = self._run_sql_json_exec_from_scratch()
superset_1        |   File "/app/superset/sqllab/command.py", line 138, in _run_sql_json_exec_from_scratch
superset_1        |     raise ex
superset_1        |   File "/app/superset/sqllab/command.py", line 133, in _run_sql_json_exec_from_scratch
superset_1        |     return self._sql_json_executor.execute(
superset_1        |   File "/app/superset/sqllab/sql_json_executer.py", line 111, in execute
superset_1        |     raise SupersetErrorsException(
superset_1        | superset.exceptions.SupersetErrorsException: [SupersetError(message="'+00'", error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'PostgreSQL', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]

Screenshots

Screenshot 2022-06-21 at 11 28 46

Environment

(please complete the following information):

  • browser type and version: Chrome 102
  • superset version: 1.5.1
  • python version: 3.8
  • node.js version: none
  • any feature flags active:

Checklist

Make sure to follow these steps before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces 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 was not an issue in the 1.4.2.
May be similar to #19995

@dheardal dheardal added the #bug Bug report label Jun 21, 2022
@dheardal
Copy link
Author

Duplicate of #20155

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

1 participant