[MGNLCE-17] Generated Identifiers Too Long for MySQL Created: 08/Jan/16  Updated: 18/Mar/16  Resolved: 18/Mar/16

Status: Closed
Project: Community Edition
Component/s: None
Affects Version/s: 5.4.3
Fix Version/s: None

Type: Bug Priority: Trivial
Reporter: John H Anderson Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: MySQL
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Fedora release 22, magnolia-community-webapp-5.4.3.war, tomcat-el-2.2-api-7.0.59-4.fc22.noarch, community-mysql-server-5.6.27-1.fc22.x86_64


Attachments: File catalina.out     XML File jackrabbit-bundle-mysql-search.xml     File magnolia.properties     File magnoliaAuthor.sql.bz2    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

Following this guide: https://wiki.magnolia-cms.com/display/WIKI/Magnolia+CMS+with+MySQL

I converted a brand new install of magnolia-community-webapp to use MySQL for the FileSystem & PersistenceManager, but not the DataStore. After altering the configurations as described in the guide, I deployed the WAR to a Tomcat server. It seemed to deploy alright, and it created schemas in the database, but then I ran into this error in Tomcat's catalina.out:

Identifier name 'FS__x002f_VAR_x002f_LIB_x002f_TOMCAT_x002f_WEBAPPS_x002f_MAGNOLIAAUTHOR_x002f_REPOSITORIES_x002f_MAG' is too long

I'm thinking that maybe some sort of foreign key constraint or index is being created, but the name is too long? I'm not really sure, and I haven't yet figured out a workaround. I'm pretty new to Magnolia. My first thought was server collation, but I've tried with both latin1 & utf-8 collations and I'm experiencing the same errors.

I've attached my tomcat logs and a dump of the generated schema, or at least the schema that had been generated up to the point the bug was triggered. I would like to attach my composed WAR, including configuration changes, but that exceeded the file size. So instead I've attached the configurations that I changed.



 Comments   
Comment by John H Anderson [ 20/Jan/16 ]

Nevermind. This issue is resolved.

I accidentally used ${wsp.home} in a path instead of ${wsp.name}. I looked and looked, and just didn't see the mistake. In any event, using the whole path caused the MySQL Schema Object identifier to be too long (i.e. > 64 chars).

My apologies for the erroneous report. I downgraded the severity because I don't think I have access to resolve & close the issue myself.

Generated at Mon Feb 12 00:05:30 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.