Thanks for the immediate reply. What exactly do you mean my "preference name". I have just followed the tutorial to build a custom portal. I have not changed anything. (??) Where can I check for that name?
-----Original Message----- From: Ate Douma (JIRA) [mailto:[email protected]] Sent: Tuesday, June 02, 2009 10:10 AM To: Vlachogiannis Evangelos Subject: [jira] Updated: (JS2-1025) Mysql maven2 build error - UNIQUE INDEX key too long [ https://issues.apache.org/jira/browse/JS2-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated JS2-1025: --------------------------- Priority: Minor (was: Major) The problem really is with MySQL, this is not a Jetspeed bug. The unique index cannot be made shorter without a complete object remodelling, we need all these columns in the index as it represent a *logical* model constraints. The fact you're overrunning the *mysql* limit of 1000 bytes key length indicates you most likely are using an extremely long preference name. I suggest trying to reduce your preference name length as easiest solution here. > Mysql maven2 build error - UNIQUE INDEX key too long > ---------------------------------------------------- > > Key: JS2-1025 > URL: https://issues.apache.org/jira/browse/JS2-1025 > Project: Jetspeed 2 > Issue Type: Bug > Components: Project Build > Affects Versions: 2.2.2 > Environment: WinXP, jdk 1.6, mysql 5.0.45 community-nt > Reporter: Evangelos Vlachogiannis > Priority: Minor > > While building a custom j2.2 portal I got the following error: > Embedded error: Failed to execute: CREATE UNIQUE INDEX > UIX_PORTLET_PREFERENCE > ON PORTLET_PREFERENCE (DTYPE, APPLICATION_NAME, PORTLET_NAME, ENTITY_ID, > USER_NA > ME, NAME) > Specified key was too long; max key length is 1000 bytes > [INFO] > ------------------------------------------------------------------------ > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Unexpected error > I think that the: > CREATE UNIQUE INDEX UIX_PORTLET_PREFERENCE ON > PORTLET_PREFERENCE (DTYPE, APPLICATION_NAME, PORTLET_NAME, ENTITY_ID, > USER_NAME, NAME) > query needs to be replaced with a shorter index e.g. (DTYPE, > APPLICATION_NAME, PORTLET_NAME) but I do not know about side effects. > Please provide fix and deploy also to jars as people cannot build custom > portals with j2.2 / mysql -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.12.48/2147 - Release Date: 06/01/09 17:55:00
