[
https://issues.apache.org/jira/browse/DERBY-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543660
]
Kim Haase commented on DERBY-3168:
----------------------------------
Thanks, Dag! I'm glad you caught traceFileAppend -- it is not mentioned in the
"Network client tracing" topic in the Admin Guide, only in the parent topic, so
I missed it. I believe it should be in the Reference Manual too. I'll add a
topic for it.
And I will revise the docs to indicate that traceDirectory and traceFile can be
used together. Maybe I'll include an example of that.
Thanks also for the confirmation on the bit mask. I guess that also means that
the column in the table is okay.
> Reference Manual lacks topics on trace-related connection URL attributes
> ------------------------------------------------------------------------
>
> Key: DERBY-3168
> URL: https://issues.apache.org/jira/browse/DERBY-3168
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.3.1.4
> Reporter: Kim Haase
> Assignee: Kim Haase
> Attachments: DERBY-3168.diff, DERBY-3168.zip
>
>
> The Admin Guide topic "Network client tracing" describes three connection URL
> attributes that enable network client tracing:
> http://db.apache.org/derby/docs/dev/adminguide/cadminappsclienttracing.html
> The URL attributes are traceFile, traceDirectory, and traceLevel.
> These three attributes are missing from the Reference Manual section where
> all the connection URL attributes are listed and described:
> http://db.apache.org/derby/docs/dev/ref/rrefattrib24612.html
> Like the securityMechanism and ssl attributes, these attributes appear to
> apply only to the client/server mode of Derby, not to the embedded mode.
> I'll add topics to the Reference Manual for each of these attributes, unless
> there is some reason not to.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
