You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2021/09/29 06:40:16 UTC

[GitHub] [superset] villebro commented on pull request #16869: fix: handle TIME column serialization

villebro commented on pull request #16869:
URL: https://github.com/apache/superset/pull/16869#issuecomment-929881598


   I'm surprised this is not happening with GAQ disabled - is this really the case? Long term we should probably introduce the option to format time values in the frontend like we do with `TIMESTAMP`/`DATE`/`DATETIME`, and to do that we would need to convert it into millisecond format like we do for `datetime`, introduce a new `GenericDataType` type called `TIME` that the frontend could then use to properly format the values. Is this something you would be willing to collaborate on @frafra ? In the mean time this could be a good compromise.


-- 
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-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org