[
https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474874
]
Kim Haase commented on DERBY-2365:
----------------------------------
Yes, I'll be glad to remove the reference to LONG VARCHAR. Should I say
explicitly that it is not supported?
I wonder if there are any other unsupported builtin data types? The topic says
MAX works "on expressions that evaluate to built-in data types (including CHAR,
VARCHAR, DATE, TIME, CHAR FOR BIT DATA, etc.)".
Hm, I wonder if MIN needs to be fixed too?? Well, I guess that would be a
separate issue.
> 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.
