empire-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Döbele (JIRA) <empire-db-...@incubator.apache.org>
Subject [jira] Resolved: (EMPIREDB-67) Allow selection of (Mysql) Database Engine
Date Thu, 25 Mar 2010 09:58:27 GMT

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

Rainer Döbele resolved EMPIREDB-67.
-----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: empire-db-2.0.7-incubating )
                   empire-db-2.0.6-incubating

Engine can be set with new property "Engine" on DBDatabaseDriverMySQL

> Allow selection of (Mysql) Database Engine
> ------------------------------------------
>
>                 Key: EMPIREDB-67
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-67
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: empire-db-2.0.5-incubating
>            Reporter: Francis De Brabandere
>             Fix For: empire-db-2.0.6-incubating
>
>
> Requested by Phil Barrett on the mailing list:
> Is there some place where from Empire-db you can tell mysql what database engine to use,
innodb, myisam etc?
> Best would be to make this somehow available per DBDatabase, adding it to the mysql driver
should be trivial. Are there any other databases that allow selecting the engine? (eg MySQL
innodb, myisam,...)

-- 
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