[
https://issues.apache.org/jira/browse/CALCITE-7337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18045575#comment-18045575
]
Julian Hyde edited comment on CALCITE-7337 at 12/16/25 5:37 PM:
----------------------------------------------------------------
[~terran2010], As [~jensen] suggested, this should be a feature. You should
change the summary and description so that it reads like a feature. Specify the
function (a link to Postgres documentation is useful, but is not sufficient),
and give an example.
Reviewers: Please do not merge the PR until the Jira case is in good shape.
was (Author: julianhyde):
[~terran2010], As [~jensen] suggested, this should be a feature. You should
change the summary and description so that it reads like a feature. Specify the
function, and give an example.
> There is no age function that supports pgSQL
> --------------------------------------------
>
> Key: CALCITE-7337
> URL: https://issues.apache.org/jira/browse/CALCITE-7337
> Project: Calcite
> Issue Type: New Feature
> Components: core
> Affects Versions: 1.41.0
> Reporter: terran2010
> Priority: Major
> Labels: pull-request-available
>
> The SQL：
> {code:java}
> SELECT AGE(timestamp '2023-12-25', timestamp '2020-01-01') as age1 FROM
> (VALUES (1)) t {code}
> result is ok:
> {code:java}
> 3 years 11 mons 24 days 0 hours 0 mins 0.0 secs {code}
> But is:
> {code:java}
> Error while executing SQL "SELECT AGE(timestamp '2023-12-25', timestamp
> '2020-01-01') as age1 FROM (VALUES (1)) t": From line 1, column 8 to line 1,
> column 58: No match found for function signature AGE(<TIMESTAMP>,
> <TIMESTAMP>) {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
