You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Tomohito Nakayama (JIRA)" <ji...@apache.org> on 2007/02/21 14:55:05 UTC
[jira] Created: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
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
Priority: Minor
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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474750 ]
Kim Haase commented on DERBY-2365:
----------------------------------
Yes, that puts it much more simply and clearly -- I think it would be more correct to say
"because the two strings compare as equal"
> 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
> Priority: Minor
>
> 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.
[jira] Commented: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475061 ]
Kim Haase commented on DERBY-2365:
----------------------------------
Bryan, thank you for those suggestions about the MAX and MIN pages, and Tomohito, thanks for renaming this issue -- that is the right thing to do.
Should I change the language in MIN about blank spaces to match the language in MAX?
> 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
> 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
> Attachments: DERBY-2365.diff, 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474728 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
Problem is that it is very difficult to translate this kind of vague expression ...
Sometimes translating them straightly results in unreadable expression in Japanese.
It can be clearer when it is translated into Japanese ...
> 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
> Priority: Minor
>
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474740 ]
Kim Haase commented on DERBY-2365:
----------------------------------
Would this be less ambiguous?
"...because a string that has one or more trailing blank spaces is treated as identical to the same string that does not have trailing blank spaces."
I know it's a bit clumsy. But a phrase beginning with "without" can be either adverbial or adjectival, so it took me a while to figure out if the "without" in Bryan's suggestion appled to the noun "string" or to the verb phrase.
I think that "because a blank space is a special value" doesn't really explain the situation.
> 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
> Priority: Minor
>
> 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.
[jira] Closed: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "Kristian Waagan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan closed DERBY-2365.
----------------------------------
> 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.1.4
> 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
> Assignee: Kim Haase
> Fix For: 10.3.1.4
>
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475007 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
Do I rename this issue as "brushing up pages for MAX / MIN in Derby Reference Manual" ?
> 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.
[jira] Updated: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomohito Nakayama updated DERBY-2365:
-------------------------------------
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.
was:
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".
Priority: Major (was: Minor)
Environment:
Max
http://db.apache.org/derby/docs/dev/ref/rrefsqlj27781.html
Min
http://db.apache.org/derby/docs/dev/ref/rrefsqlj33520.html
was:http://db.apache.org/derby/docs/dev/ref/rrefsqlj27781.html
Summary: Brushing up pages for MAX and MIN in Derby Reference Manual (was: Example of MAX in Derby Reference Manual is not explained appropriately)
> 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
> 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
> Attachments: DERBY-2365.diff, 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.
[jira] Updated: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "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.
[jira] Commented: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478085 ]
Kim Haase commented on DERBY-2365:
----------------------------------
Thank you very much! I'll mark the issue resolved, then.
> 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
> 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
> 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.
[jira] Updated: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-2365:
-----------------------------
Attachment: DERBY-2365.zip
DERBY-2365-2.diff
Attaching DERBY-2365-2.diff and DERBY-2365.zip with the changes to the MIN and MAX function descriptions. I kept finding more places where the two files were inconsistent for no obvious reason, so I've made them consistent where I can. There's one difference where I'm not sure which word is correct, though:
MAX is an aggregate function that evaluates the maximum of the expression over a set of values ...
MIN is an aggregate function that evaluates the minimum of an expression over a set of rows ...
Which should it be, values or rows? They may both be correct, but we should pick one.
(I'll change "the expression" to "an expression" for MAX, too. I just noticed that!)
> 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
> 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
> Attachments: DERBY-2365-2.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.
[jira] Assigned: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase reassigned DERBY-2365:
--------------------------------
Assignee: Kim Haase
> 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
>
> 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.
[jira] Updated: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-2365:
-----------------------------
Attachment: rrefsqlj27781.html
DERBY-2365.diff
Attaching DERBY-2365.diff file and HTML output file rrefsqlj27781.html, with the corrected wording.
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase resolved DERBY-2365.
------------------------------
Resolution: Fixed
> 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
> 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
> 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.
[jira] Commented: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477614 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
I think there are no problem for this patch.
Sending src/ref/rrefsqlj27781.dita
Sending src/ref/rrefsqlj33520.dita
Transmitting file data ..
Committed revision 514156.
> 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
> 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
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475015 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
I found another problem in page for MIN.
There exists next sentence :
The type's comparison rules determine the maximum value.
Here, maximum should be minimum.
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474866 ]
Bryan Pendleton commented on DERBY-2365:
----------------------------------------
Thanks Kim! The diff and HTML page look good to me.
As long as we're working on this page, does anybody know the answer to Dan's question about LONG VARCHAR? Is that datatype allowable for a MAX?
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475016 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
I came to feel it would be good to cluster brushing up issue for those.
I will rename this 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474752 ]
Kim Haase commented on DERBY-2365:
----------------------------------
Dan's phrasing is better (I was responding to the previous post, not his).
("comparisons" is the correct spelling)
> 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
> Priority: Minor
>
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474744 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
I think we are too thinking about *value* itself .....
How about "because they are of equal in comparison" ?
> 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
> Priority: Minor
>
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-2365:
-----------------------------
Attachment: DERBY-2365-2.zip
DERBY-2365-3.diff
I think I figured it out -- I made the first sentence of MAX consistent with the first sentences of the other aggregate functions ("the maximum of an expression over a set of rows").
Sorry about the odd numbering: the final patch is DERBY-2365-3.diff and DERBY-2365-2.zip. Please let me know if anything still needs fixing. I hope this is ready to commit now.
> 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
> 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
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474755 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
I see.
I will translate Dan's phrase into Japanese.
> 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
>
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474726 ]
Bryan Pendleton commented on DERBY-2365:
----------------------------------------
Perhaps:
"because one or more trailing blank spaces at the end of a character string do not distinguish it from the same string without the trailing blanks".
Does a wording like that make the meaning any clearer?
> 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
> Priority: Minor
>
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474733 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
By the way, is the meaning of the sentence different ,
if it was replaced as "because a blank space is a special value" ?
If so , I can translate the sentence as if it was replaced without replacing in English.
Sorry for confusing discussion ...
> 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
> Priority: Minor
>
> 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.
[jira] Updated: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim Haase updated DERBY-2365:
-----------------------------
Derby Info: [Patch Available]
> 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
> 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
> Attachments: DERBY-2365-2.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.
[jira] Commented: (DERBY-2365) Brushing up pages for MAX and MIN in
Derby Reference Manual
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475071 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
Reading page for MIN,
I feel that similar description for trailing blank spaces should be in the page for MIN as the page for MAX.
// It may be verbose to have similar description in each pages ,
// but I think that verboseness is prefered in the reference manual.
> 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
> 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
> Attachments: DERBY-2365.diff, 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474732 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
"No value" may be recognized as "value which may be ignored" in English, I think .
But in sence of Japanese word usage, no value is just null.
Then the sentence can be directly translated as "because a blank space is null" ...
// This may be nonsence because this is English and not Japanese ...
> 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
> Priority: Minor
>
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Tomohito Nakayama (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474703 ]
Tomohito Nakayama commented on DERBY-2365:
------------------------------------------
Mistaken ....
"because a blank space is a special value"
> 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
> Priority: Minor
>
> 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.
[jira] Commented: (DERBY-2365) Example of MAX in Derby Reference
Manual is not explained appropriately
Posted by "Daniel John Debrunner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12474748 ]
Daniel John Debrunner commented on DERBY-2365:
----------------------------------------------
how about:
"because trailing spaces are ignored for character comparisions"
PS. Can long varchar be used in a MAX?
> 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
> Priority: Minor
>
> 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.