[
https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474867
]
Bryan Pendleton commented on DERBY-2365:
----------------------------------------
OK, I tried it, and I think LONG VARCHAR is *not* supported for MAX:
ij> create table D2365 (a int, b varchar (20), c char(10), d long varchar);
0 rows inserted/updated/deleted
ij> select max(a) from d2365;
1
-----------
NULL
1 row selected
ij> select max(b) from d2365;
1
--------------------
NULL
1 row selected
ij> select max(c) from d2365;
1
----------
NULL
1 row selected
ij> select max(d) from d2365;
ERROR 42Y22: Aggregate MAX cannot operate on type LONG VARCHAR.
Kim, what do you think about revising your patch to remove the reference to
LONG VARCHAR as well?
> 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.
