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

Michael Bouschen updated JDO-766:
---------------------------------
    Fix Version/s:     (was: JDO 3.2)

> Support more JDBC-aware databases in JDO TCK
> --------------------------------------------
>
>                 Key: JDO-766
>                 URL: https://issues.apache.org/jira/browse/JDO-766
>             Project: JDO
>          Issue Type: New Feature
>          Components: tck
>    Affects Versions: JDO 3.1
>         Environment: non-Derby databases with RI (DataNucleus)
>            Reporter: Craig L Russell
>            Priority: Minor
>
> The TCK does not support databases except for Derby, even though the RI does.
> The primary blocker is that the TCK uses an embedded Derby database.
> The proposed solution is to use a JDBC connection to the database instead of 
> an embedded Derby database. 
> There are a few issues:
> - Before running the TCK, the database will need to be started, which may 
> involve a manual operation or a database-dependent script. And after the TCK 
> test completes, the database will need to be shut down.
> - The database schema need to be created, which currently uses a 
> Derby-specific program. This program needs to be replaced by a program that 
> reads a SQL command file containing the SQL commands to create the schema. 
> And the schema needs to be created manually or automatically based on 
> metadata.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to