[ https://issues.apache.org/jira/browse/JCR-1435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740526#action_12740526 ]
Stefan Guggisberg commented on JCR-1435: ---------------------------------------- i'd rather provide a custom ddl on the classpath and refer to it in the configuration, e.g. <param name="schema" value="mysql-custom" /> suggested on the user list: http://www.mail-archive.com/us...@jackrabbit.apache.org/msg12089.html > Choose the MySQL engine for database storage (default to MyISAM) > ---------------------------------------------------------------- > > Key: JCR-1435 > URL: https://issues.apache.org/jira/browse/JCR-1435 > Project: Jackrabbit Content Repository > 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-2008-04-28.patch, > jackrabbit-1.4.x-mysql-engine.patch, > jackrabbit-trunk-mysql-engine-2008-04-28.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.