jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thomas Mueller <muel...@adobe.com>
Subject Re: Warning! The maximum key length is 900 bytes
Date Fri, 13 May 2011 07:59:08 GMT

Unless you use extremely long workspace names (longer than 500
characters), this warning is not a problem. Jackrabbit doesn't generate
entries with a long path and name (longer than 900 characters).

However, I think we should change the script to something like:
FSENTRY_PATH varchar(700), FSENTRY_NAME varchar(150) - so that you don't
get a warning.

Could you create an issue about this at
https://issues.apache.org/jira/browse/JCR ?


On 5/13/11 9:40 AM, "emiliano albiani" <EmilianoAlbiani@tagetik.com> wrote:

>Hi all,
>We are using the DBMS as filesystem and we had a look at the tables
>created by Jackrabbit when working with Microsoft SQL Server.
>The Jackrabbit's SQL script:
>create unique index ${schemaObjectPrefix}FSENTRY_IDX on
>${schemaObjectPrefix}FSENTRY (FSENTRY_PATH, FSENTRY_NAME) ${tableSpace},
>creates an index on FSENTRY_PATH which is a column of the table create by
>the script:
>create table ${schemaObjectPrefix}FSENTRY (FSENTRY_PATH varchar(2048) not
>null, FSENTRY_NAME varchar(255) not null, FSENTRY_DATA image null,
>FSENTRY_LASTMOD bigint not null, FSENTRY_LENGTH bigint not null)
>We noticed that the FSENTRY_PATH column's length exceed the maximum size
>of index keys 
>Could we face any problem?
>Is anyone aware of this warning?
>Thanks in advance.

View raw message