Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 99226 invoked from network); 16 Aug 2007 09:52:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Aug 2007 09:52:03 -0000 Received: (qmail 19310 invoked by uid 500); 16 Aug 2007 09:52:00 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 19287 invoked by uid 500); 16 Aug 2007 09:52:00 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 19278 invoked by uid 99); 16 Aug 2007 09:52:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Aug 2007 02:52:00 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Aug 2007 09:52:12 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6EE807141E2 for ; Thu, 16 Aug 2007 02:51:30 -0700 (PDT) Message-ID: <13377280.1187257890426.JavaMail.jira@brutus> Date: Thu, 16 Aug 2007 02:51:30 -0700 (PDT) From: "Stefan Guggisberg (JIRA)" To: dev@jackrabbit.apache.org Subject: [jira] Commented: (JCR-1049) DatabaseFileSystem: mysql.ddl works for mysql5 but not mysql 4.1.20 In-Reply-To: <24983564.1186000373143.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ 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. 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. 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.