[ 
https://issues.apache.org/jira/browse/DERBY-5000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kim Haase resolved DERBY-5000.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.8.0.0
    Issue & fix info:   (was: [Known fix])

Having heard no objections, committed patch DERBY-5000.diff to documentation 
trunk at revision 1087841. May as well get it into 10.8.

Suddenly realized I had forgotten to mark this patch available. (Wish we still 
got those daily emails about issues with patch available status.) My apologies. 

> The Derby properties section in the reference manual should provide hint 
> about where to find server specific properties.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5000
>                 URL: https://issues.apache.org/jira/browse/DERBY-5000
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Dag H. Wanvik
>            Assignee: Kim Haase
>            Priority: Minor
>             Fix For: 10.8.0.0
>
>         Attachments: DERBY-5000.diff, crefproper22250.html
>
>
> When referring to the reference manual looking for explanation of Derby 
> properties, one finds the section. "Derby properties", whose first sentence 
> reads:
> "The Derby properties are used for configuring the system and database, as 
> well as for diagnostics such as logging statements, and monitoring and 
> tracing locks."
> There is no mention of server specific properties (these are explained in the 
> "Setting Network Server properties" in the server manual).
> Still, these are "Derby properties" and would be perceived as such by many 
> users, so I think this section in the reference manual should 
> point the user to the server manual also: This section does, after all,  
> *not* explain all Derby properties. The tools properties are probably not 
> necessary to mention/crosslink from here.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to