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-461) Network Client Driver 'password=' behaviour is different from Embedded Driver
Date Fri, 15 Jul 2005 14:33:10 GMT
    [ http://issues.apache.org/jira/browse/DERBY-461?page=comments#action_12315924 ] 

Philip Wilder commented on DERBY-461:

There seem to be two places clientside where password length is checked:

If length == 0 conditionals are removed my Standalone repro seems to work properly. Anyone
know of any hidden ramifications this might have?

I also checked getting a connection through a ClientDataSource without problem. Can anyone
think of anymore clientside connection methods I should be testing? 

> Network Client Driver 'password=' behaviour is different from Embedded Driver
> -----------------------------------------------------------------------------
>          Key: DERBY-461
>          URL: http://issues.apache.org/jira/browse/DERBY-461
>      Project: Derby
>         Type: Bug
>   Components: Network Client
>     Versions:
>     Reporter: Susan Cline
>     Priority: Minor
>  Attachments: Derby461.java
> I posted to derby-dev asking if this was a bug and did not receive any response, so I'm
logging it as a bug.
> Using the Embedded driver and specifying password= for the driver URL does not throw

> an exception or warning:
> ij> connect 'jdbc:derby:myDB;create=true;user=a;password=';
> Using this syntax with the Network Client driver does:
> ij> connect 'jdbc:derby://localhost:1527/blobDB;user=a;password=';
> ERROR (no SQLState): password length, 0, is not allowed.
> This bug is a request to make the behaviour of the client driver the same as the embedded

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