[
https://issues.apache.org/jira/browse/CALCITE-5366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17630039#comment-17630039
]
Julian Hyde commented on CALCITE-5366:
--------------------------------------
Thanks for the test case. It's helpful.
Regarding qualifying functions with a schema. I believe that Calcite uses a
different path for functions than it does for tables. This is by design (and
consistent with the ISO SQL standard). The default schema does not and should
not affect function resolution.
> User defined function optional named arguments are required to be present
> -------------------------------------------------------------------------
>
> Key: CALCITE-5366
> URL: https://issues.apache.org/jira/browse/CALCITE-5366
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.32.0
> Reporter: Tuomas Kiviaho
> Priority: Major
>
> In situation where optional parameters are stated before the required ones
> the {{FamilyOperandTypeChecker#getOperandCountRange}} prohibits leaving these
> arguments undefined.
> Would it be possible to have {{getOperandCountRange}} reporting only the
> number of non-optional parameters in case named parameters are used.
> The current behavior might indeed be in line with SQL99 SQL:1999 Part 2
> Section 10.4 as the {{SqlUtil#lookupSubjectRoutines}} states, but the current
> behavior kind of beats the flexibility that named parameters provide.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
