[ http://issues.apache.org/jira/browse/DERBY-384?page=comments#action_12314442 ]
Stan Bradbury commented on DERBY-384: ------------------------------------- Stan's Review of: %%% Tuning Guide: Derby properties >> ON PAGE: http://incubator.apache.org/derby/docs/tuning/ctunproper51399.html Scope of Derby properties ADD TEXT under the system-wide section bullet point labeled: ' Set in the derby.properties file ' ** TEXT TO ADD: The derby.properties file is an optional file that can be created to set properties at the system level when the Derby driver is loaded. Derby looks for this file in the directory defined by the derby.system.home property thus any property EXCEPT derby.system.home can be set by including it in this file. >> ON PAGE: http://incubator.apache.org/derby/docs/tuning/rtunproper13217.html derby.infolog.append ** CHANGE THE FIRST SENTENCE FROM: Specifies whether to append to or destroy and re-create the derby.log file, which is used to record error and other information when Derby starts up in a JVM. ** NEW TEXT: Specifies whether to append to or overwrite (delete and recreate) the derby.log file when the Derby engine is started. The derby.log file is used to record error and other information. This information can be important when debugging problems with a system. >> On PAGE: http://incubator.apache.org/derby/docs/tuning/rtunproper27355.html derby.user.UserName ** REMOVE THIS EXTRA (nonsense) TEXT FROM THE EXAMPLE: ..... -- cache a userDN locally derby.user.richard=uid=richard, ou=People, o=JBMSTours.com .... ** LOCATOR NOTE: Below is the nonsense text w/ surrounding lines: 'derby.user.sa', 'Derby3x9')-- cache a userDN locally derby.user.richard=uid=richard, ou=People, o=JBMSTours.com -- cache a userDN locally, database-level property ** CHANGE THE LINK LABEL: 'Caching user DNs ' to the new title specified in the next note (Note on Cacheing user DNs) >> ON PAGE: http://incubator.apache.org/derby/docs/tuning/rtunpropercachedn.html Caching user DNs ** CHANGE TITLE OF PAGE TO: Note on Cacheing user DNs > Doc Review: Tuning Derby > ------------------------ > > Key: DERBY-384 > URL: http://issues.apache.org/jira/browse/DERBY-384 > Project: Derby > Type: Improvement > Components: Documentation > Environment: all > Reporter: Jeff Levitt > Priority: Minor > Fix For: 10.1.1.0 > > This issue tracks comments for the manual known as Tuning Derby. The deadline > for posting comments is Tuesday, June 28, noon Pacific time. > Some guidelines to follow when posting comments to this issue are: > - Try to make clear and concise comments about what you want changed whenever > possible. Provide concrete comments that say "Please change <original> to > <modified>" instead of generic comments like "This section needs to be > rewritten." > - If you're reviewing the HTML Files copy, include the URL for the page in > the review comment. Obtain the URL like this: > * highlight the topic in the left frame > * right click > * choose "Properties" > * copy and paste the address in the pop up box. > - If you're reviewing the PDF copy, in the review comment: > * Include the page number for the PDF, and indicate whether the number is > the PDF sheet number or the printed page number. > * Include the title of the section that the problem occurs in. If it's in > a subsection, try to include the hierarchy of titles. > - Please don't review the HTML Book copy -- it'll be time consuming to match > up that copy with the underlying DITA source. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
