Fix SQL generation for long schema names
----------------------------------------
Key: NXP-8111
URL: https://jira.nuxeo.com/browse/NXP-8111
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: Core SQL Storage
Affects Versions: 5.4
Environment: MySQL
Reporter: Florent Guillaume
Assignee: Florent Guillaume
Fix For: 5.5
When using extremely long schema (or complex type) names, databases that have
limits on their system name lengths (table names, constraint names, index
names) may fail.
For instance MySQL:
{noformat}
Caused by: org.nuxeo.ecm.core.api.WrappedException: Exception:
java.sql.SQLException. message: Error post creating table: ALTER TABLE
`cmdist_initial_copy_external_participant_mailboxes` ADD INDEX
`cmdist_initial_copy_external_participant_mailboxes_id_hierarchy_fk` (`id`),
ADD CONSTRAINT
`cmdist_initial_copy_external_participant_mailboxes_id_hierarchy_fk` FOREIGN
KEY (`id`) REFERENCES `hierarchy` (`id`) ON DELETE CASCADE : Identifier name
'cmdist_initial_copy_external_participant_mailboxes_id_hierarchy_fk' is too long
at
org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.createTables(JDBCMapper.java:224)
at
org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.createDatabase(JDBCMapper.java:142)
... 38 more
Caused by: org.nuxeo.ecm.core.api.WrappedException: Exception:
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException. message: Identifier
name 'cmdist_initial_copy_external_participant_mailboxes_id_hierarchy_fk' is
too long
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
