db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Satheesh Bandaram (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-307) create=true in client connect throws ex if database exists
Date Thu, 02 Jun 2005 21:02:52 GMT
     [ http://issues.apache.org/jira/browse/DERBY-307?page=comments#action_66918 ]
Satheesh Bandaram commented on DERBY-307:

I can't reproduce this bug. DerbyClient allows connecting to a database with "create=true"
URL attribute, even if it already exists. Embedded driver also allows connecting to database
with the same attribute even if the database is already present. But in the case of Embedded
driver, a Warning is raised. Network server currently doesn't raise some warnings, so Derbyclient
doesn't show similar warning as embedded driver.

So, I don't think there is a bug here (other than the network server issue, which is not specific
to create=true). Not sure if there is an improvement Jira entry to get network server to show

I will attach my test case to this Jira entry.

> create=true in client connect throws ex if database exists
> ----------------------------------------------------------
>          Key: DERBY-307
>          URL: http://issues.apache.org/jira/browse/DERBY-307
>      Project: Derby
>         Type: Bug
>   Components: Network Client
>     Versions:
>     Reporter: Jeremy Boynes
>  Attachments: Test.java
> An attempt to connect to a network database with create=true results in an exception
if the database exists; with the embedded server a warning is raised.

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