Yep, I can reproduce the problem - and think I localized the area where the bug is.
The current .../driver/sqlite.clj uses regex pattern matching, so it matches type strings beginning with some patterns. There is - probably just by oversight - no definition for “TIMESTAMP” - so it will drop through the list until it hits … yeah, you guessed right: “TIME”…
@zooond thanks for surfacing this. I think, until someone can fix this, your options are either to move to another database driver, drop to native SQL and select datetime(time, 'unixepoch') from your_timestamp_table or convert it to a DateTime which should work.
I have just experienced the same issue running Metabase… v0.34.3, and a SQLite file exported via Python’s sqlite3.
in Custom Question:
Despite being defined as either “Creation Date”, “Creation Timestamp”, the date appears as “8:00PM”-like.
in SQL query:
The datetime(time, 'unixepoch') workaround doesn’t work, but simply selecting the column in a SQL query actually returns a timestamp.
Yet I believe the bug has been solved in the meantime, right?