db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6424) Document thenExpression
Date Tue, 13 May 2014 14:13:18 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996416#comment-13996416

Kim Haase commented on DERBY-6424:

It appears from the syntax in DERBY-6423 (a little hard to figure out because of what JIRA
does with vertical bars), a thenExpression can be either a valueExpression or NULL. I guess
that is also the case for an elseExpression (which we also don't define).

We define a valueExpression in exactly one place, the "generationClause" topic under CREATE
TABLE, which is the only place it is currently used. I assume I can use the same definition
("A valueExpression is an expression that resolves to a single value") -- are there any limitations
similar to those in that topic? The function ones, for example?

> Document thenExpression
> -----------------------
>                 Key: DERBY-6424
>                 URL: https://issues.apache.org/jira/browse/DERBY-6424
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Dag H. Wanvik
>            Assignee: Kim Haase
> The reference manual uses the grammar non-terminal "thenExpression" as a place holder
for the result of a CASE... THEN <result>, but it is nowhere defined.
> When the parent issue DERBY-6423 is fixed, this production should be defined accordingly.
(The lack of a definition was discovered while investigating that issue.)

This message was sent by Atlassian JIRA

View raw message