[
https://issues.apache.org/jira/browse/DERBY-5640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240736#comment-13240736
]
Kim Haase commented on DERBY-5640:
----------------------------------
One of the Tuning manual topics with tables poses a terminology question, I
think for Knut Anders.
In the topic "Transaction-based lock escalation"
(http://db.apache.org/derby/docs/10.8/tuning/ctunoptimz42065.html) each of the
three tables has a column with the head "Promote?" The term "promote" or
"promotion" is not used anywhere else in the Tuning manual, and the question
being answered is whether the system will escalate to table-level locking. Is
it okay if in addition to adding a description, I change the column head to
"Escalate?"
Thanks!
> Use <desc> element for table summary
> ------------------------------------
>
> Key: DERBY-5640
> URL: https://issues.apache.org/jira/browse/DERBY-5640
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Affects Versions: 10.8.2.2, 10.9.0.0
> Reporter: Kim Haase
> Assignee: Kim Haase
> Priority: Minor
> Fix For: 10.8.2.2
>
> Attachments: DERBY-5640-2.diff, DERBY-5640-2.stat, DERBY-5640-2.zip,
> DERBY-5640-3.diff, DERBY-5640-3.stat, DERBY-5640-3.zip, DERBY-5640-4.diff,
> DERBY-5640-4.stat, DERBY-5640-4.zip, DERBY-5640.diff, DERBY-5640.stat,
> DERBY-5640.zip
>
>
> Currently we provide table summaries by putting the table caption in the
> summary. However, the <desc> element should be used for this purpose.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
