Details
-
Bug
-
Resolution: Not an issue
-
Trivial
-
None
-
5.4.3
-
None
-
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
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.