[
https://issues.apache.org/jira/browse/DERBY-2603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493530
]
Kim Haase commented on DERBY-2603:
----------------------------------
There are references to these operators as binary on the following pages:
http://db.apache.org/derby/docs/dev/ref/rrefsqlj13733.html (CHAR data type):
same sentence as in http://db.apache.org/derby/docs/dev/ref/rrefsqlj41207.html
(VARCHAR data type)
http://db.apache.org/derby/docs/dev/ref/rrefsqlj1083019.html (Where dynamic
parameters are allowed):
"5. For the binary operators +, -, *, /, AND, OR, <, >, =, <>, <=, and >=, use
of a dynamic parameter as one operand but not both is permitted. Its type is
taken from the other side."
So the use of "binary" to mean "having two operands" is intentional.
But perhaps the word "binary" can simply be removed from rrefsqlj13733 and
rrefsqlj41207 -- don't all comparison operators have two operands? If so,
"binary" is not necessary to the meaning here.
> Minor erratum in page of VARCHAR in Derby Reference manual
> ----------------------------------------------------------
>
> Key: DERBY-2603
> URL: https://issues.apache.org/jira/browse/DERBY-2603
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Environment:
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj41207.html
> Reporter: Tomohito Nakayama
> Priority: Minor
>
> I found next statement in the page through translation into Japanese.
> > When binary comparison operators are applied to VARCHARs, the lengths of
> > the operands are not altered, and spaces at the end of the values are
> > ignored.
> I think "binary" should be replaced as "boolean".
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
