Tables for schemas with long names should be shortened correctly for Oracle
---------------------------------------------------------------------------
Key: NXP-6102
URL: https://jira.nuxeo.org/browse/NXP-6102
Project: Nuxeo Enterprise Platform
Issue Type: Bug
Components: Core SQL Storage
Affects Versions: 5.3 GA
Reporter: Florent Guillaume
Assignee: Florent Guillaume
Priority: Major
Fix For: 5.4.1
When using a schema with a very long name, the table in Oracle is not using an
appropriately shortened name which leads to:
ERROR [MCFConnectionInterceptor] Error occurred creating ManagedConnection for
org.apache.geronimo.connector.outbound.connectioni...@bec438
org.nuxeo.ecm.core.storage.StorageException: java.sql.SQLException: ORA-00972:
identifier is too long
at
org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.createDatabase(JDBCMapper.java:133)
at
org.nuxeo.ecm.core.storage.sql.jdbc.JDBCBackend.newMapper(JDBCBackend.java:156)
at
org.nuxeo.ecm.core.storage.sql.RepositoryImpl.getConnection(RepositoryImpl.java:335)
...
Caused by: java.sql.SQLException: ORA-00972: identifier is too long
...
at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1552)
at
org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.createTables(JDBCMapper.java:199)
at
org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.createDatabase(JDBCMapper.java:130)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.nuxeo.org/secure/Administrators.jspa
-
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
