jackrabbit-dev mailing list archives

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

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

Stefan Guggisberg resolved JCR-1049.

    Resolution: Won't Fix
      Assignee: Stefan Guggisberg

hi stephen,

thanks for reporting this issue.

this issue has been reported a while ago on the dev-list. you can find the
discussion (incl. solutions) here:

i'm resolving this issue as "Won't Fix" since it's IMO rather a db configuration issue.


> 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