jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sébastien Launay (JIRA) <j...@apache.org>
Subject [jira] Commented: (JCR-1435) Choose the MySQL engine for database storage (default to MyISAM)
Date Thu, 28 Feb 2008 13:47:51 GMT

    [ https://issues.apache.org/jira/browse/JCR-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573280#action_12573280

Sébastien Launay commented on JCR-1435:

Sure, but this setting is global, so we can not have a database with default tables
to NDB and another with default to InnoDB.

Moreover it's interesting to not touch the RDBM and having the tables created
automatically in the wanted engine, especially for developers or for easier deployment.

> Choose the MySQL engine for database storage (default to MyISAM)
> ----------------------------------------------------------------
>                 Key: JCR-1435
>                 URL: https://issues.apache.org/jira/browse/JCR-1435
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-core
>    Affects Versions: core 1.4.1
>         Environment: MySQL with NDB Cluster engine
>            Reporter: Sébastien Launay
>         Attachments: jackrabbit-1.4.x-mysql-engine.patch, jackrabbit-trunk-mysql-engine.patch
> The MySQL scripts embedded into Jackrabbit does not specify the engine to use.
> So by default MyISAM is used and we cannot change this.
> But, depending on the environment we may want to use an alternate engine like
> InnoDB (for transaction support) or in my case NDB Cluster (for high availability).
> We can still manually created the tables and then set the wanted engine, but it would
> be better if there was a parameter for the engine for component in the repository.xml
> for automatic table creation.

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

View raw message