jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1049) DatabaseFileSystem: mysql.ddl works for mysql5 but not mysql 4.1.20
Date Thu, 20 Sep 2007 18:19:31 GMT

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

Jukka Zitting updated JCR-1049:
-------------------------------

    Affects Version/s: 1.2.1
                       1.2.2
                       1.2.3
                       1.3.1
        Fix Version/s: 1.3.2

Merged to the 1.3 branch in revision 577850.

> 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.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1
>         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
>             Fix For: 1.3.2
>
>
> 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.


Mime
View raw message