<< Back to previous view

[NUCRDBMS-465] Schema generation when having single table per inheritance tree and subclass has primitive field creates invalid schema Created: 11/Nov/10  Updated: 13/Nov/10  Resolved: 11/Nov/10

Status: Closed
Project: DataNucleus Store RDBMS
Component/s: ORM, Schema
Affects Version/s: 2.1.2, 2.2.0.m2
Fix Version/s: 2.1.3, 2.2.0.m3

Type: Bug Priority: Major
Reporter: Andy Jefferson Assignee: Unassigned
Resolution: Fixed Votes: 0


 Description   
When we have

class Base
{
   ...
}
class Sub extends Base
{
   int primitiveField;
}

this tries to do an "ALTER TABLE ADD COLUMN PRIMITIVE FIELD NOT NULL". When part of the subclass and using table of superclass needs to either have a default value, or be nullable. The user could easily workaround this by marking the column nullability, but better to do it ourselves.

 Comments   
Comment by Andy Jefferson [ 11/Nov/10 02:39 PM ]
SVN trunk and branches/2.1 have this
Generated at Thu Jan 18 01:17:49 CET 2018 using JIRA 4.0#466.