[
https://issues.apache.org/jira/browse/CALCITE-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17882492#comment-17882492
]
Julian Hyde commented on CALCITE-6585:
--------------------------------------
I agree. Again, this issue will improve performance, but is not urgent. The
comprehensive tests you have written are a great foundation for this work, if
and when someone wants to take on this refactoring.
{quote}This sequence is analogous to a compiled RegEx pattern and could be
cached{quote}
Note that the BigQuery {{PARSE_TIMESTAMP}} and {{FORMAT_DATE}} functions, which
are very similar to {{TO_CHAR}}, are already implemented using this pattern.
> In the Postgres TO_CHAR function, improve caching
> -------------------------------------------------
>
> Key: CALCITE-6585
> URL: https://issues.apache.org/jira/browse/CALCITE-6585
> Project: Calcite
> Issue Type: Improvement
> Reporter: Julian Hyde
> Assignee: Norman Jordan
> Priority: Major
>
> In the Postgres TO_CHAR function (and similar functions added in
> CALCITE-6358), cache the formatter using the same technique used in
> CALCITE-5914.
> Also pass the {{DataContext}} into the constructor of {{class
> DataFormatFunction}}, so that it does not need to be passed to each call to
> {{toCharPg}}.
> In {{DateFormatFunction}} obsolete static field {{LOCAL_ZONE}} and instead
> populate a non-static field {{zoneId}} from the {{DataContext}} constructor
> parameter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
