Alice-608 opened a new issue, #37925: URL: https://github.com/apache/superset/issues/37925
### Bug description In the latest master branch of Apache Superset, datetime-type fields exhibit inconsistent and incorrect behavior when used in visualizations, compared to raw SQL queries in SQL Lab: SQL Lab: When executing a raw SELECT query on a table containing datetime data, the time values are returned correctly as stored in the database. Datasets & Charts: When the same data is used to create a dataset and visualizations (eg:Bar Charts, Scatter Plots): The datetime values displayed on the chart are incorrect. The time deviation is inconsistent across different data points. Some timestamps are shifted by hours, while others are shifted by days, with no uniform offset. Concrete example from the provided screenshots: <img width="1123" height="789" alt="Image" src="https://github.com/user-attachments/assets/c989d9ec-cc2e-4e5f-9686-add3aaf40dee"; /> <img width="1271" height="684" alt="Image" src="https://github.com/user-attachments/assets/fed38cef-cbd8-431c-b692-7895420245ba"; /> <img width="1278" height="665" alt="Image" src="https://github.com/user-attachments/assets/7726e88d-79f2-4492-8207-fbb51b51aadf"; /> This discrepancy breaks the reliability of time-based visualizations and makes it impossible to trust the results. Expected Behavior Datetime fields should display consistent, correct time values in both SQL Lab and all visualizations, regardless of the time grain or grouping used. The time shown in the chart should exactly match the time returned by the raw SQL query. Actual Behavior SQL Lab: Time values are correct and match the source data. Charts: Time values are incorrect and do not reflect the source data. Deviations are inconsistent across different data points, with shifts of varying hours and even days. ### Screenshots/recordings _No response_ ### Superset version master / latest-dev ### Python version 3.9 ### Node version 16 ### Browser Chrome ### Additional context _No response_ ### Checklist - [ ] I have searched Superset docs and Slack and didn't find a solution to my problem. - [ ] I have searched the GitHub issue tracker and didn't find a similar bug report. - [ ] 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: [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]
