[
https://issues.apache.org/jira/browse/DERBY-6394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805338#comment-13805338
]
Kim Haase commented on DERBY-6394:
----------------------------------
In the "Boolean expressions" section of the main "SQL expressions" topic,
retain only the first two sentences and a sentence that links to the main
"Boolean expressions" topic.
In the "Boolean expressions" topic itself, include the first two sentences of
the "Boolean expressions" section of the main "SQL expressions" topic. List the
other places where these expressions occur in addition to WHERE clauses and
check constraints: CASE expressions, the HAVING clause, ON clauses of INNER
JOIN/LEFT OUTER JOIN/RIGHT OUTER JOIN operations (and add the WHEN clause when
implementing DERBY-6390).
I gather we may not even need a separate searchCondition topic. Knut suggests
that we link to the Boolean expressions topic instead, from most places. The
information in the current searchCondition topic (under "CONSTRAINT clause")
should be moved into the columnLevelConstraint and tableLevelConstraint topics,
where it makes more sense anyway, since it mentions the constraintName
argument. The link to searchCondition in the HAVING clause is actually
incorrect, since the information in the searchCondition topic is specific to
constraints. So the HAVING clause should link to the "Boolean expressions"
topic instead.
> Fix problems with searchCondition and Boolean expression documentation in
> Reference Manual
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-6394
> URL: https://issues.apache.org/jira/browse/DERBY-6394
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.10.1.1
> Reporter: Kim Haase
> Assignee: Kim Haase
>
> In DERBY-6390, Knut Anders Hatlen suggests some organizational fixes to the
> Reference Manual documentation of searchConditions and Boolean expressions.
> I'll detail these in a comment.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
