[
https://issues.apache.org/jira/browse/CALCITE-6958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Xu updated CALCITE-6958:
---------------------------
Summary: JDBC adapter for MySQL not support floor date to
MILLISECOND/MICROSECOND (was: JDBC adapter for Mysql not support floor date to
MILLISECOND/MICROSECOND)
> JDBC adapter for MySQL not support floor date to MILLISECOND/MICROSECOND
> ------------------------------------------------------------------------
>
> Key: CALCITE-6958
> URL: https://issues.apache.org/jira/browse/CALCITE-6958
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.39.0
> Reporter: Yu Xu
> Assignee: Yu Xu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.40.0
>
>
> Currently Mysql not support floor date to MILLISECOND/MICROSECOND
> as we know Mysql max timestamp precision is 6, so it should be floor date to
> MICROSECOND
> it test well in Mysql system:
> *max precision:*
> {code:java}
> select DATE_FORMAT(NOW(6) , '%Y-%m-%d %H:%i:%s.%f')
> > 2025-04-14 19:01:08.708101{code}
>
> *floor date to MILLISECOND:*
> {code:java}
> SELECT SUBSTRING(DATE_FORMAT(NOW(6) , '%Y-%m-%d %H:%i:%s.%f') , 1, 23);
> > 2025-04-14 19:18:25.216 {code}
> *floor date to MICROSECOND:*
> {code:java}
> SELECT SUBSTRING(DATE_FORMAT(NOW(6) , '%Y-%m-%d %H:%i:%s.%f') , 1, 26);
> > 2025-04-14 19:19:25.265661{code}
> but current version we can only floor date to SECOND, we may need to support
> to floor date to MILLISECOND/MICROSECOND
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
