[
https://issues.apache.org/jira/browse/JCR-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520024
]
Stefan Guggisberg commented on JCR-1049:
----------------------------------------
> Mysql fixed this bug ( not config ) as of 5.0.19 -
> http://bugs.mysql.com/bug.php?id=13835
this mysql bug is IMO unrelated to the current issue because it refers to
fulltext indices which are not used in jackrabbit.
fulltext indices don't have a size limit (hence the mysql bug), but regular
indices do.
> 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.
