Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <19470195.1181644826654.JavaMail.jira@brutus>
Date: Tue, 12 Jun 2007 03:40:26 -0700 (PDT)
From: "Myrna van Lunteren (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Assigned: (DERBY-391) Tools and Utilities guide does not
 document ij.datasource, ij.user, nor ij.password
In-Reply-To: <1089819056.1119563350481.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Myrna van Lunteren reassigned DERBY-391:
----------------------------------------

    Assignee: Myrna van Lunteren

> 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
>         Attachments: derby391firsthalf.diff, rtoolsijproprefdatasource.html, rtoolsijproprefpassword.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.