> Does anyone know why the Oracle dialect doesn't generate table names that > match the Oracle specification?
In all fairness there are two problems here: 1. The Oracle platform has a fundamental 30-character limit on identifiers. 2. The Hibernate Oracle dialects (OracleDialect, Oracle9Dialect) generate identifiers by default that do not respect this well-known platform limitation. The Hibernate folks seem pretty unwilling to address their problem: - http://opensource.atlassian.com/projects/hibernate/browse/HHH-355 - http://opensource.atlassian.com/projects/hibernate/browse/ANN-563 While ANN-563 suggests naming strategies are pluggable, DefaultComponentSafeNamingStrategy is apparently the only one they provide. Rolling your own naming strategy seems a poor substitute for controlling the schema directly via annotation properties or a mapping file. Which brings us back to my suggestion. Using an XML mapping file in lieu of annotations would solve this issue, and provide a configuration point for others that need or want more control over the database schema for registered services and other RDMBS-capable CAS components. The build considerations I mentioned seem one obstacle to that approach; are there others? Marvin _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
