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] Updated: (DERBY-461) Network Client Driver 'password=' behaviour is different from Embedded Driver
Date Tue, 19 Jul 2005 12:05:46 GMT
     [ http://issues.apache.org/jira/browse/DERBY-461?page=all ]

Philip Wilder updated DERBY-461:

    Attachment: Derby461.patch

I poked around the DRDA specs a bit looking for any reference to password lengths without
much luck. If there is any inherant problem with passwords of length 0 then this patch is
no good, otherwise it has potential. It has been testing against derbyall, the error was the
known Derby-273 problem. It should be noted that JCC still does not like 0 length passwords.

> 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, Derby461.patch
> 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