[
https://issues.apache.org/jira/browse/JCR-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520187
]
Stefan Guggisberg commented on JCR-1049:
----------------------------------------
> mysql4.dll and mysql.ddl should have:
> create unique index JCR_FSENTRY_IDX on JCR_FSENTRY (FSENTRY_PATH(745),
> FSENTRY_NAME);
that's not a good idea since the max key limit is storage engine & mysql
version dependant.
<quote src="http://dev.mysql.com/doc/refman/4.1/en/create-index.html";>
Prefix lengths are storage engine-dependent (for example, a prefix can be up to
1000 bytes long for MyISAM tables, 767 bytes for InnoDB tables). (Before MySQL
4.1.2, the limit is 255 bytes for all tables.) Note that prefix limits are
measured in bytes, whereas the prefix length in CREATE INDEX statements is
interpreted as number of characters for non-binary data types (CHAR, VARCHAR,
TEXT). Take this into account when specifying a prefix length for a column that
uses a multi-byte character set.
</quote>
the current 'create unique index' stmt in mysql.ddl is IMO a good compromise
that will work with most mysql servers out there.
> 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.
