You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Stefan Guggisberg (JIRA)" <ji...@apache.org> on 2007/08/02 14:52:52 UTC
[jira] Updated: (JCR-1049) DatabaseFileSystem: mysql.ddl works for
mysql5 but not mysql 4.1.20
[ https://issues.apache.org/jira/browse/JCR-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Guggisberg updated JCR-1049:
-----------------------------------
Component/s: core
Summary: DatabaseFileSystem: mysql.ddl works for mysql5 but not mysql 4.1.20 (was: mysql.ddl works for mysql5 but not mysql 4.1.20)
> 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
>
> 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.