db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3105) No documentation of ij -ca option
Date Wed, 13 Feb 2008 23:05:18 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568744#action_12568744

Kathey Marsden commented on DERBY-3105:

A little bit of ancient history on this.  The -ca option was introduced to be able to pass
JCC attributes and Cloudscape attributes in ij.  It used to be that you could not specify
both client and embedded attributes in the JCC url.  I think the -ca option doesn't really
add value and should be deprecated (removed from the usage message) and not documented.

> No documentation of ij -ca option
> ---------------------------------
>                 Key: DERBY-3105
>                 URL: https://issues.apache.org/jira/browse/DERBY-3105
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Sebb
>            Assignee: Abhilash T.G
>            Priority: Minor
> The ij tool gives the following help output:
> Usage: java org.apache.derby.tools.ij [-p propertyfile] [-ca connectionAttributePropertyFile]
> The -p flag and inputfile are documented in "derbytools.pdf", but the -ca flag does not
seem to be documented anywhere.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message