[OPENJPA-1725] Schemaname wrongly included in DBDictionary.checkNameLength after Tablename correctly truncated

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.2, 1.3.0, 2.0.0, 2.1.0
• Fix Version/s: 2.1.1, 2.2.0
• Environment: Linux, J2SE, OracleDB 10.2.0.1, JDBC drivers 10.2.0.1, 11.2.0.1, 10.2.0.4, OpenJPA versions as listed above
• Assignee: Michael Dick
• Reporter: Joerg Knoche
• Created: 14/Jul/10 09:24
• Updated: 17/Aug/11 08:51
• Resolved: 11/May/11 20:57

Description

While enhancing and mapping files for an Oracle database the tablenames are correctly truncated after 30 characters (or whatever I write as maxTableNameLenght in the DBDictionary), the check in DBDictionary.checkNameLength includes the name of the schema which is used, therefore exceeding and failing the check for 30 characters by (length of schemaname +1) (see exception below).

Exception in thread "main" <openjpa-2.0.0-r422266:935683 nonfatal user error> org.apache.openjpa.util.UserException: Table name "TEST.LS_DETPOINT_WITH_ORIENTATIONDA" is 35-character long. The database allows maximum 30-character for a table name.
[java] at org.apache.openjpa.jdbc.sql.DBDictionary.checkNameLength(DBDictionary.java:5215)
[java] at org.apache.openjpa.jdbc.sql.DBDictionary.getCreateTableSQL(DBDictionary.java:3304)
[java] at org.apache.openjpa.jdbc.sql.OracleDictionary.getCreateTableSQL(OracleDictionary.java:899)
[java] at org.apache.openjpa.jdbc.schema.SchemaTool.createTable(SchemaTool.java:956)

Issue Links

• is related to: OPENJPA-866 DBDictionary.maxTableNameLength is not checked when using SynchronizeMappings
• relates to: OPENJPA-2038 Do not include schema name when calculating table name length by default.