db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-406) Client DataSource should not require user property to be set
Date Wed, 06 Jul 2005 20:17:13 GMT
    [ http://issues.apache.org/jira/browse/DERBY-406?page=comments#action_12315174 ] 

Daniel John Debrunner commented on DERBY-406:

I meant, prior to the client data sources, Derby's embedded implementation of DataSource apis
did not have the concept for default values for any of their Java Bean properties. Thus this
default concept is new to Derby.
Note that the Derby *engine* provides the default of APP for the user name., not EmbeddedDataSource.
Its getUser method (corrresponding to its user property) will return null for a newly created

So I'm not saying defaults are bad, just that we need to define what happens if the property
is set to null, does it mean the property returns to its default value, or does it take on
the null value? The point about no prior defaults means there is no prior behaviour to follow.

> 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