JackRabbit tables on MySql - MyISAM vs InnoDB

[sbarriba <sb...@yahoo.co.uk>]

Hi all,

The DDL for MySql doesn't specify MyISAM or InnoDB.

As a result it uses the default table type which is usually MyISAM I
believe.

 

Anyone have any issues / comments with using InnoDB instead with JackRabbit?

 

Regards,

Shaun

 

 

Re: JackRabbit tables on MySql - MyISAM vs InnoDB

[Sébastien Launay <se...@anyware-tech.com>]

Hi,

I totally agree that the engine must be included in the script,
this is why i created an improvement in JIRA a while ago.
Moreover MyISAM cannot be used in a cluster configuration
because there will be no lock on the journal tables and this
could produce multiple entries with the same revision number.

You can find a patch here:
http://issues.apache.org/jira/browse/JCR-1435

--
Sébastien Launay

sbarriba wrote:
> Hi all,
>
> The DDL for MySql doesn't specify MyISAM or InnoDB.
>
> As a result it uses the default table type which is usually MyISAM I
> believe.
>
>  
>
> Anyone have any issues / comments with using InnoDB instead with JackRabbit?
>
>  
>
> Regards,
>
> Shaun
>   

Re: JackRabbit tables on MySql - MyISAM vs InnoDB

[Stefan Guggisberg <st...@day.com>]

hi shaun

On Mon, Sep 22, 2008 at 1:27 PM, sbarriba <sb...@yahoo.co.uk> wrote:
> Hi all,
>
> The DDL for MySql doesn't specify MyISAM or InnoDB.

you can use your own customized ddl file. the ddl file is looked up
in the same package as the persistence manager class.

an example for the bundle MySqlPersistenceManager:

- create a mymysql.ddl resource in the package
  o.a.j.c.persistence.bundle,
- adapt your pm config (schema="mymysql"),
- add your resource to the class path.

cheers
stefan

>
> As a result it uses the default table type which is usually MyISAM I
> believe.
>
>
>
> Anyone have any issues / comments with using InnoDB instead with JackRabbit?
>
>
>
> Regards,
>
> Shaun
>
>
>
>
>
>