db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2576) setCreateDatabase does not work for EmbeddedXADataSource or EmbeddedConnectionPoolDataSource
Date Fri, 20 Apr 2007 18:47:15 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel John Debrunner updated DERBY-2576:
-----------------------------------------

    Issue Type: Bug  (was: Improvement)

I think this is a bug because these classes extend EmbeddedDataSource and thus inherit the
behaviour of that class which includes the setCreateDatabase() method and its intended behavior.

> setCreateDatabase does not work for EmbeddedXADataSource or EmbeddedConnectionPoolDataSource
> --------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2576
>                 URL: https://issues.apache.org/jira/browse/DERBY-2576
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.3.0.0
>            Reporter: Myrna van Lunteren
>            Priority: Minor
>         Attachments: DERBY-2576_tst.diff
>
>
> After implementing setCreateDatabase for ClientDataSource, and creating a test (see DERBY-2296)
I realized there was no such test for XADataSource or ConnectionPoolDataSource.
> However, the test I created failed with Embedded, because the database does not get created.
A database *does* get created using setConnectionAttributes(create=true). 
> Also, setShutdownDatabase does work (tested in XADSAuthenticationTest and PoolDSAuthenticationTest).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message