[
https://issues.apache.org/jira/browse/DERBY-4446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-4446:
-----------------------------
Attachment: DERBY-4446.diff
rrefsqlj30118.html
rrefsqlj15147.html
Attaching a patch that fixes the problem in these two topics, with the two
output files.
> Clarify reference manual regarding specifying field length of LONG VARCHAR
> columns
> ----------------------------------------------------------------------------------
>
> Key: DERBY-4446
> URL: https://issues.apache.org/jira/browse/DERBY-4446
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 10.5.3.0, 10.6.0.0
> Reporter: Kristian Waagan
> Assignee: Kim Haase
> Priority: Minor
> Attachments: DERBY-4446.diff, rrefsqlj15147.html, rrefsqlj30118.html
>
>
> When creating columns of type LONG VARCHAR or LONG VARCHAR FOR BIT DATA, you
> are not allowed to specify the maximum length of the data. The current
> wording in the reference manual may be read as that you can set the maximum
> length, but that you don't have to. We should state that specifying the
> length is not allowed for these two data types.
> From https://bugs.eclipse.org/bugs/show_bug.cgi?id=286206 :
> The Derby manual I referred to said "you do not have to specify a maximum
> length when creating columns of this type". What they actually meant is "you
> cannot specify a maximum length"!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
