Unable to view created_at and updated_at field values

[ramandamodar12]

Metabase Version - 0.33

Unable to view the raw values of created_at and updated_at fields of any table in my MySQL database.

[flamber]

Hi @ramandamodar12
The screenshot is not Metabase 0.33 (not even released yet) - latest is 0.32.9 - so what are you using?
Have you defined formatting, otherwise try setting it again? Admin > Settings > Formatting
What is the default language of your browser?

[ramandamodar12]

Hi @ramandamodar12
The screenshot is not Metabase 0.33 (not even released yet) - latest is 0.32.9 - so what are you using?
Have you defined formatting, otherwise try setting it again? Admin > Settings > Formatting
What is the default language of your browser?

The settings page shows the version as 0.33.0-snapshot.

Sharing the screenshot of the global level format settings.

The default language is set to EN

[flamber]

@ramandamodar12
Okay, that doesn't show which branch+commit you're using. Are you reporting an issue with master?
Why are you not using one of the pre-built releases? https://metabase.com/start/

[ramandamodar12]

@flamber I had followed the steps shown at https://metabase.com/docs/latest/operations-guide/running-metabase-on-elastic-beanstalk.html#deploying-new-versions-of-metabase to update metabase. This file was downloaded https://downloads.metabase.com/v0.32.9/metabase-aws-eb.zip and was updated in the AWS console. Not sure why the settings page shows 0.33.

[flamber]

@ramandamodar12
Okay, something must have gone wrong somewhere. Can you verify that the file Dockerrun.aws.json inside metabase-aws-eb.zip is using the image metabase/metabase:v0.32.9?
Also, click the gear-icon ⚙️ in top right corner and click "About Metabase", which should tell you version and commit version and built date.

[amis47]

we just updated to 0.32.8 as well and it ran into the same problem

fwiw

[flamber]

@amis47
Which version did you upgrade from?
Are you using MySQL too? Which version?
Is this only a problem with Native (SQL) or does it also happens with Custom question?
Does it work if you change the field formatting in visualization settings ⚙️?

[amis47]

thanks for your quick response, we upgraded metabase from 0.31.2 to 0.32.8. All SQL statement seems to work fine, the only problem is we are unable to see datetime field such as created_at / updated_at field values.

[flamber]

@amis47
Does the created_at/updated_at use microseconds? Where column type is like datetime(6)
Which version of MySQL?
Reference: https://discourse.metabase.com/t/datetime-values-not-rendering-in-results-table/6869

[ramandamodar12]

@amis47
Does the created_at/updated_at use microseconds? Where column type is like datetime(6)
Which version of MySQL?
Reference: https://discourse.metabase.com/t/datetime-values-not-rendering-in-results-table/6869

Yes @flamber The fields use microseconds. As a workaround, we are using DATE_FORMAT function.

[salsakran]

Closing as this was fixed in 0.33 based on that discourse conversation.

If it reappears chime in here and we'll reopen

[dannymc129]

Hate to do this @salsakran but I just upgraded today from 0.31.2 to 0.33.3 and this issue popped up. It's a very interesting one, I noticed that a datetime that specifically have microseconds of 000 does return from the /datasets but all others don't. I guess 1/1000 ain't bad right?

I reverted all the way back to 0.33.0-rc1 and this still occurs.

[flamber]

@dannymc129
Are you still seeing this problem on 0.33.6? Is it specific to Custom or Native question?
I cannot reproduce this problem with MySQL 5.7.28 column type datetime(6) (0.32.9 thru 0.33.6)

[flamber]

Is anyone able to reproduce this problem on the latest release 0.34.3 ?