okayhooni opened a new issue, #28685: URL: https://github.com/apache/superset/issues/28685
### Bug description when get value with `TIMESTAMP WITH TIME ZONE` type from Trino, `db_engine_specs/presto.py` code of Superset cannot handle that value properly. (please see the screenshot below.) I found some issues and MR to fix this issue. - https://github.com/apache/superset/pull/19263 - https://github.com/apache/superset/pull/21737 But the modified codes with PR above, is removed on the PR below - https://github.com/apache/superset/pull/22871 ### How to reproduce the bug just submit a query like below, to Trino. ``` SELECT now() as server_time, now() at time zone 'UTC' as utc_time, now() at time zone 'Asia/Seoul' as seoul_time, -- wrong CAST(now() at time zone 'Asia/Seoul' as TIMESTAMP WITH TIME ZONE) as seoul_time_2, -- wrong CAST(now() at time zone 'Asia/Seoul' as TIMESTAMP) as seoul_time_3 -- valid ``` ### Screenshots/recordings  ### Superset version 3.1.3 ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context https://superset.apache.org/docs/configuration/timezones/ ### Checklist - [X] I have searched Superset docs and Slack and didn't find a solution to my problem. - [X] I have searched the GitHub issue tracker and didn't find a similar bug report. - [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section. -- 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: notifications-unsubscr...@superset.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org For additional commands, e-mail: notifications-h...@superset.apache.org
