You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Chunwei Lei (JIRA)" <ji...@apache.org> on 2019/04/15 12:56:00 UTC

[jira] [Commented] (CALCITE-947) Allow optional parameters to have default values other than NULL

    [ https://issues.apache.org/jira/browse/CALCITE-947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16817938#comment-16817938 ] 

Chunwei Lei commented on CALCITE-947:
-------------------------------------

[~julianhyde], Does anyone work on this issue? If no one, I would like to take this issue.

> Allow optional parameters to have default values other than NULL
> ----------------------------------------------------------------
>
>                 Key: CALCITE-947
>                 URL: https://issues.apache.org/jira/browse/CALCITE-947
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Priority: Major
>
> As of CALCITE-941 user-defined functions can have optional parameters and you can omit them or use the DEFAULT keyword. But the default value must be NULL, and therefore the parameter must have an optional type.
> This case would remove that restriction and allow default values which are literals, or calls to system functions (e.g. USER) or references to other parameters, or expressions composed thereof.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)