jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen More (JIRA)" <j...@apache.org>
Subject [jira] Reopened: (JCR-1049) DatabaseFileSystem: mysql.ddl works for mysql5 but not mysql 4.1.20
Date Thu, 02 Aug 2007 16:02:54 GMT

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

Stephen More reopened JCR-1049:

I am sorry, but IMO this does not seem like a reasonable solution.

Mysql fixed this bug ( not config ) as of 5.0.19 - http://bugs.mysql.com/bug.php?id=13835

To support older databases, mysql4.ddl should get created with:
create table ${schemaObjectPrefix}FSENTRY (FSENTRY_PATH text not null, FSENTRY_NAME varchar(255)
not null, FSENTRY_DATA longblob null, FSENTRY_LASTMOD bigint not null, FSENTRY_LENGTH bigint
not null) charset latin1

This allows the developer to choose the right schema in his/her application without having
to download the code, create a patch, then do it all over again after the next release.

mysql4.dll and mysql.ddl should have:

> DatabaseFileSystem: mysql.ddl works for mysql5 but not mysql 4.1.20
> -------------------------------------------------------------------
>                 Key: JCR-1049
>                 URL: https://issues.apache.org/jira/browse/JCR-1049
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.3
>         Environment: MySQL 4.1.20
> ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes
>            Reporter: Stephen More
>            Assignee: Stefan Guggisberg
> Perhaps a new column ( primary key ) could get added to the table called uid, which is
actually an md5checksum of FSENTRY_PATH and FSENTRY_NAME.

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

View raw message