[jira] Updated: (DERBY-2365) Brushing up pages for MAX and MIN in Derby Reference Manual

["Kathey Marsden (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-2365:
----------------------------------

    Affects Version/s: 10.3.0.0
        Fix Version/s: 10.3.0.0

> 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
>    Affects Versions: 10.3.0.0
>         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
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY-2365-2.diff, DERBY-2365-2.zip, DERBY-2365-3.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.