[
https://issues.apache.org/jira/browse/DERBY-4280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim Haase updated DERBY-4280:
-----------------------------
Attachment: DERBY-4280.zip
DERBY-4280.stat
DERBY-4280.diff
Attaching DERBY-4280.diff, DERBY-4280.stat, and DERBY-4280.zip, with changes as
follows:
M src/ref/refderby.ditamap
M src/ref/crefproper22250.dita
A src/ref/rrefproperstatementcachesize.dita
M src/tuning/ctundepth32379.dita
I created a topic for the derby.language.statementCacheSize property and added
a bit of info to the Tuning Derby topic on the statement cache. If there are
other logical places to put more info, please let me know.
I found the default value of the property in the Derby code, but I made some
not very educated guesses on the scope of the property and whether it is
dynamic or static (see the "Derby properties" topic as well as the topic for
the property). Probably some of this needs fixing.
I could not find a logical place in the Developer's Guide to mention this
subject; there are several topics on deadlocks, and after that some topics on
multi-threaded applications, but none seemed quite right. Suggestions are
welcome.
Please let me know what needs changing or adding.
> Property not documented - derby.language.statementCacheSize
> -----------------------------------------------------------
>
> Key: DERBY-4280
> URL: https://issues.apache.org/jira/browse/DERBY-4280
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.5.1.1
> Environment: N/A
> Reporter: Jeff Stuckman
> Assignee: Kim Haase
> Priority: Trivial
> Attachments: DERBY-4280.diff, DERBY-4280.stat, DERBY-4280.zip
>
>
> The property derby.language.statementCacheSize is not documented in any of
> the Derby documentation.
> This property may be useful for tuning Derby.
> In addition, setting this property to 0 is vital for working around
> DERBY-4279, and its lack of documentation makes it more difficult for users
> to discover this workaround.
--
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
