Postgres timestamp and character 'T'

[ziggekatten]

I have an simple issue, and that I can't get timestamp columns to show hour, minutes and seconds in for example an table chart.

Data example with an 'select * from' in SQL Lab:

Adaptive formatting in table chart just gives me the date:

Trying to change from adaptive format, hour, minutes and seconds are all replaced with zeros. It seems that Superset by default do not understand ISO format?

Or I am missing something simple here? Superset version 4.0.2

[dosubot[bot]]

I found a similar closed issue regarding timestamp formats being displayed as NaN:NaN:NaN, but no solution was found in the comments. You can view the issue here ^[1].

To display timestamps with hours, minutes, and seconds in a table chart in Superset version 4.0.2, you can use the D3 time format option '%Y-%m-%d %H:%M:%S'. This format will ensure that the hours, minutes, and seconds are shown instead of being replaced with zeros. You should select this format option in your Superset chart configuration ^[2].

Additionally, the table_timestamp_format setting in the table chart configuration can override the timestamp display settings. This setting allows you to choose a D3 time format for datetime columns, and it can be customized using the available D3_TIME_FORMAT_OPTIONS ^[3].

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[ziggekatten]

@dosu, '%Y-%m-%d %H:%M:%S' is what I used in my tests, but it still gives 00:00:00.

[dosubot[bot]]

There are a few potential reasons why the time portion of your timestamps might be defaulting to 00:00:00 in Superset:

1. Timezone Handling: Superset assumes timestamps are in UTC, and if the database or the data source is not explicitly handling timezones, it might lead to discrepancies in the displayed time. Ensure that your data source is correctly configured to handle timezones ^[1].

2. Specific Logic in Superset: There is logic in Superset's codebase that might set the time to 00:00:00 under certain conditions, such as when parsing dates or handling specific date strings like 'today' ^[2].

3. Configuration Overrides: Check if there are any global or column-specific settings in your Superset configuration that might override the D3 time format settings. The table_timestamp_format setting can override the timestamp display settings, so ensure it is set correctly ^[3].

4. Data Source Configuration: Verify that the data source itself is not altering the timestamp format. Sometimes, the way data is fetched or processed can affect how timestamps are displayed.

If these suggestions don't resolve the issue, it might be helpful to review the data source configuration and any transformations applied to the data before it reaches Superset.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[ziggekatten]

I looked at the generated SQL for my chart, and did DATE_TRUNC on my columns. Scratching my head back and forth, and the problem is really not that complicated: If you have an time grain defined on the chart, there will not bee any hours, minutes or seconds to apply D3 format to. Removing time grain and hey presto!