db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John H. Embretsen (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-391) Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password
Date Tue, 12 Jun 2007 11:26:26 GMT

    [ https://issues.apache.org/jira/browse/DERBY-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12503835
] 

John H. Embretsen commented on DERBY-391:
-----------------------------------------

Thanks for doing this, Myrna! 
I've taken a look at the new html pages. The one for ij.showNoCountForSelect seems OK to me,
although it is a bit confusing since the property name is negative, so the reader has to do
some extra thinking. I don't have any better suggestions for the docs, so I think it is ready
for commit.

The other page, for ij.showNoConnectionsAtStart, I think has a couple of issues:

1) Here too, the property name is negative (showNoConnections...), which is confusing. Under
Function, it says: "Default is true, that is, a message indicating the current connections,
if any, is displayed." However, if ij.showNoConnectionsAtStart is true, it means "Show no
connections at start", which means that no connections are displayed. I think the default
is false, so the correct description should be: "Default is false, that is, a message indicating
the current connections, if any, is displayed."

2) The first example has a typo, missing "No" in the property name, that is -Dij.showConnectionsAtStart=true
should be -Dij.showNoConnectionsAtStart=true.

3) I think the output for the two example commands should switch places, that is, when the
property is true no connection message is displayed. When the property is false, a connection
message is displayed.


> Tools and Utilities guide does not document ij.datasource, ij.user, nor ij.password
> -----------------------------------------------------------------------------------
>
>                 Key: DERBY-391
>                 URL: https://issues.apache.org/jira/browse/DERBY-391
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.1.1.0
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.3.0.0
>
>         Attachments: DERBY-391.diff, derby391firsthalf.diff, rtoolsijproprefdatasource.html,
rtoolsijproprefpassword.html, rtoolsijproprefshownoconn.html, rtoolsijproprefshownoselectcount.html,
rtoolsijproprefuser.html
>
>
> The Tools and Utilities guide documents the ij properties. 
> However, it does not have any documentation about the following properties
> ij.datasource
> ij.password
> ij.user
> I suggest something like this (but someone else should review):
> ij.dataSource
> Function
> This property allows one to specify the datasource that should be used to access the
database. When specifying a datasource, Derby does *not* use the DriverManager mechanism to
establish connections. For more information about DataSources, refer to the JDBC documentation
and to the Derby Developer's Guide, section Using Derby as a J2EE Resource Manager.
> To establish a connection using ij.dataSource, you need to use additional ij.dataSource
properties to set some additional properties:
> ij.dataSource.databaseName
> ij.dataSource.createDatabase
> Syntax 
> ij.dataSource=<datasourcename> ij.dataSource.databaseName=<databaseName>
[ij.dataSource.createDatabase=create]
> Example
> java -Dij.dataSource=org.apache.derby.jdbc.EmbeddedDataSource
> -Dij.dataSource.databaseName=toursDB -Dij.dataSource.createDatabase=create"
> ij.password
>   Function
>   Specifies the password used to make connections with.
>   When you connect like this, and ij creates the database, you will allways need to know
that password in order to access the database, unless you set up additional users. For more
information about authentication see the Derby Developer's Guide.
> Syntax 
> ij.pasword=password
> Example
> java -Dij.user=me -Dij.password=mine org.apache.derby.tools.ij
> See also
> ij.user; Derby Developer's Guide - Derby and Security
> ij.user
>   Function
>   Specifies the user with which connections are made by default.
>   When you connect like this, ij assumes that the database schema to be used is the same
as the username provided. However, certain database objects cannot be created until a schema
exists, i.e. until a create schema <name> has been issued, followed by a set schema
<name>, or fully qualifying the database objects to be created. If no user is specified,
no set schema has been issued, or create statements do not qualify the schema, all database
objects are assumed to be under schema 'APP'. 
> Syntax 
> ij.user=username
> Example
> java -Dij.user=me -Dij.password=mine org.apache.derby.tools.ij
> ij version 10.1
> ij> set schema finance;
> ij> select * from accounts;
> ij.password; Derby Developer's Guide - Derby and Security

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


Mime
View raw message