[ http://issues.apache.org/jira/browse/DERBY-391?page=all ]
Jeff Levitt updated DERBY-391: ------------------------------ Attachment: rtoolsijproprefdatasource.html rtoolsijproprefuser.html rtoolsijproprefpassword.html Attached is a patch for the original issue. The three html files are for review. Thanks! > Tools and Utilities guide does not document ij.datasource, ij.user, nor > ij.password > ----------------------------------------------------------------------------------- > > Key: DERBY-391 > URL: http://issues.apache.org/jira/browse/DERBY-391 > Project: Derby > Type: Improvement > Components: Documentation > Versions: 10.1.1.0 > Reporter: Myrna van Lunteren > Priority: Minor > Fix For: 10.2.0.0 > Attachments: 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira