Issue Details (XML | Word | Printable)

Key: DERBY-4025
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Kim Haase
Reporter: Kristian Waagan
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Derby

CHAR data type documentation fails to describe the maximum allowed length

Created: 19/Jan/09 08:11 AM   Updated: 04/May/09 06:22 PM
Component/s: Documentation
Affects Version/s: 10.5.1.1
Fix Version/s: 10.5.1.1

Time Tracking:
Not Specified

File Attachments:
  Size
File Licensed for inclusion in ASF works DERBY-4025-2.diff 2009-01-22 09:38 PM Kim Haase 2 kB
File Licensed for inclusion in ASF works DERBY-4025.diff 2009-01-21 09:48 PM Kim Haase 2 kB
HTML File Licensed for inclusion in ASF works rrefsqlj13733.html 2009-01-22 09:38 PM Kim Haase 4 kB
HTML File Licensed for inclusion in ASF works rrefsqlj13733.html 2009-01-21 09:48 PM Kim Haase 4 kB
Issue Links:
Reference
 

Resolution Date: 23/Jan/09 04:24 PM


 Description  « Hide
The section on CHAR fails to document the maximum allowed length.
In addition to not specifying the correct maximum length, the section can be interpreted as specifying Integer.MAX_VALUE as the maximum length of a CHAR column.

See http://db.apache.org/derby/docs/dev/ref/ref-single.html#rrefsqlj13733

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Kim Haase added a comment - 21/Jan/09 09:48 PM
Attaching DERBY-4025.diff and rrefsqlj13733.html, which add the limit of 254 characters to the syntax information and remove the misleading statement near the end. Hope this does the job.

Kristian Waagan added a comment - 22/Jan/09 10:17 AM
The changes look good to me.
One question:
Do you consider the example to belong under "Implementation-defined aspects", or can that heading/section be removed now that the misleading statement has been removed.

Kim Haase added a comment - 22/Jan/09 08:06 PM
Thanks, Kristian. I was wondering about that heading myself -- I think it may make sense to just call it "Example" instead, unless it really does show implementation-specific behavior. However, that seems unlikely. I'll file a revised patch.

Kim Haase added a comment - 22/Jan/09 09:38 PM
Attaching a revised patch, DERBY-4025-2.diff and an updated rrefsqlj13733.html. Made the suggested fix and added another example.

Kristian Waagan added a comment - 23/Jan/09 09:57 AM
I think the revised patch looks better.
+1 to commit

Thanks, Kim!

Kim Haase added a comment - 23/Jan/09 04:24 PM
Thanks, Kristian!

Committed patch DERBY-4025-2.diff to documentation trunk at revision 737068.

Kristian Waagan added a comment - 26/Jan/09 08:11 AM
Thank you, Kim!
I confirmed the change in all three variants of the reference manual.

Closing the issue.