[DERBY-2365] Brushing up pages for MAX and MIN in Derby Reference Manual

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: Documentation

Environment

Max
http://db.apache.org/derby/docs/dev/ref/rrefsqlj27781.html

Min
http://db.apache.org/derby/docs/dev/ref/rrefsqlj33520.html

• Issue & fix info: Patch Available
• Assignee: Camilla Haase
• Reporter: Tomohito Nakayama
• Created: 21/Feb/07 13:53
• Updated: 17/Nov/09 08:56
• Resolved: 05/Mar/07 16:04

Description

• 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.