When specifying a single table inheritance strategy, the model should detect
and signal potential conflicts across columns
--------------------------------------------------------------------------------------------------------------------------
Key: OPENJPA-827
URL: https://issues.apache.org/jira/browse/OPENJPA-827
Project: OpenJPA
Issue Type: Improvement
Components: jpa
Affects Versions: 1.2.0
Environment: JPA 1.2 running in Tomcat 6.14
Reporter: Benjamin Renaud
Priority: Minor
When you have Entity A with a single-table inheritance strategy it would be
nice if, when modeling B, C, D ... as subclasses of A JPA would make sure that
there are no two columns with clashing names and incompatible types. For
example, if B has a field Date defaultValue and C has a field Long defaultValue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
