[
https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474875
]
Bryan Pendleton commented on DERBY-2365:
----------------------------------------
I think we should just remove the reference to LONG VARCHAR from that one
paragraph.
MIN does indeed appear to have the same situation.
ij> select min(d) from d2365;
ERROR 42Y22: Aggregate MIN cannot operate on type LONG VARCHAR.
I think we could go ahead and address that now, if you want. I don't know that
a separate issue is necessary; the basic issue here involves the paragraph on
trailing space handling and it's the same paragraph in both doc pages.
Although, curiously, the page for MIN has slightly different text:
" For CHAR, VARCHAR, and LONG VARCHAR, the number of blank spaces
at the end of the value can affect the result."
> Example of MAX in Derby Reference Manual is not explained appropriately
> -----------------------------------------------------------------------
>
> Key: DERBY-2365
> URL: https://issues.apache.org/jira/browse/DERBY-2365
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Environment:
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj27781.html
> Reporter: Tomohito Nakayama
> Assigned To: Kim Haase
> Priority: Minor
> Attachments: DERBY-2365.diff, rrefsqlj27781.html
>
>
> 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".
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
