db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Wilder (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-406) Client DataSource should not require user property to be set
Date Mon, 04 Jul 2005 12:58:10 GMT
    [ http://issues.apache.org/jira/browse/DERBY-406?page=comments#action_12315009 ] 

Philip Wilder commented on DERBY-406:

Sorry for any redundancy on this issue but I would like to make sure that everyone is on the
same page as per the status of this patch.

The July 1 patch makes the following changes:

- Set user to default to "APP"
- Set the default servername to "localhost"
- Changed
 databaseName_ = dataSource.getDatabaseName() + attrString;
 databaseName_ = dataSource.getDatabaseName() + ";" + attrString;
 in the connection class to avoid database names like myDBcreate=true when the setConnectionAttributes
method is used.
- Changed the dataSourcePermissions_net to include additional tests to check bug fixes and
changed the associated.out file to match new output.
- Commented sections of code associated with the fixes
- Provided javadoc for new methods in dataSourcePermissions_net.java and the getPassword()
method in ClientBaseDataSource.java
- Changed the password, user and servername attributes to private so as to hopefully not conflict
with his changes, as per his "Client data source published api javadoc cleanup" email. 

> Client DataSource should not require user property to be set
> ------------------------------------------------------------
>          Key: DERBY-406
>          URL: http://issues.apache.org/jira/browse/DERBY-406
>      Project: Derby
>         Type: Bug
>   Components: Network Client
>     Versions:,
>     Reporter: Kathey Marsden
>     Assignee: Philip Wilder
>  Attachments: DataSourceNoUser.java, Derby406_409_410.patch
> ClientDataSource should not require user to be set.  It should default to user APP as
described in:
> http://incubator.apache.org/derby/docs/adminguide/cadminappsclient.html
> This all seems to work ok for for DriverManager connections but fails for ClientDataSource

> run the attached repro 
> $ java DataSourceNoUser
> embedded no userid/password
> client userid/password set
> client no password
> client no userid/no password
> org.apache.derby.client.am.SqlException: null userid not supported
>         at org.apache.derby.client.net.NetConnection.checkUser(NetConnection.java:998)
>         at org.apache.derby.client.net.NetConnection.flowConnect(NetConnection.java:380)
>         at org.apache.derby.client.net.NetConnection.initialize(NetConnection.java:233)
>         at org.apache.derby.client.net.NetConnection.<init>(NetConnection.java:201)
>         at org.apache.derby.jdbc.ClientDataSource.getConnection(ClientDataSource.java:156)
>         at org.apache.derby.jdbc.ClientDataSource.getConnection(ClientDataSource.java:135)
>         at DataSourceNoUser.main(DataSourceNoUser.java:42)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message