[
https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-2365:
-----------------------------
Attachment: DERBY-2365.zip
DERBY-2365-2.diff
Attaching DERBY-2365-2.diff and DERBY-2365.zip with the changes to the MIN and
MAX function descriptions. I kept finding more places where the two files were
inconsistent for no obvious reason, so I've made them consistent where I can.
There's one difference where I'm not sure which word is correct, though:
MAX is an aggregate function that evaluates the maximum of the expression over
a set of values ...
MIN is an aggregate function that evaluates the minimum of an expression over a
set of rows ...
Which should it be, values or rows? They may both be correct, but we should
pick one.
(I'll change "the expression" to "an expression" for MAX, too. I just noticed
that!)
> Brushing up pages for MAX and MIN in Derby Reference Manual
> -----------------------------------------------------------
>
> Key: DERBY-2365
> URL: https://issues.apache.org/jira/browse/DERBY-2365
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Environment: Max
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj27781.html
> Min
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj33520.html
> Reporter: Tomohito Nakayama
> Assigned To: Kim Haase
> Attachments: DERBY-2365-2.diff, DERBY-2365.diff, DERBY-2365.zip,
> rrefsqlj27781.html
>
>
> * Description of rules for trailing blank spaces
> In this part, next sentence of an example exists.
> For example, if the values 'z' and 'z ' are both stored in a column, you
> cannot control which one will be returned as the maximum, because a blank
> space has no value.
> Because blank space is value, I think "because a blank space has no value" is
> not appropriate.
> I think it should be as "because a blank space is an special value".
> * Mistaken information for LONG VARCHAR data type
> Now MAX / MIN are not allowed for LONG VARCHAR in Derby.
> However the manual mentions they are allowed.
> * mistaken maximum for MIN
> There exists next sentence in page for MIN :
> > The type's comparison rules determine the maximum value.
> Here, maximum should be minimum.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
