This setup is hardly legal for single-table inheritance. Either your
table has a non-null or it doesn't. If you want it your way, factor
out the fields into some extra table, mark them as "allows null" or
fix up the sql yourself.
Cheers, Anjo
Am 30.07.2006 um 13:53 schrieb Guido Neitzer:
> Entity Person exits. Entity AppUser inherits (Single Table
> Inheritance) from it and defines two additional attributes (besides
> others): login and password. They are set to "not null". EOModeler
> and Entity Modeler generate wrongs sql for this: they set login and
> password to be not null in the database too, so you can't create
> Person instances anymore as they don't know anything about the
> attributes.
>
> But I like to have them marked as "not null" because with this I
> get validation messages from EOF about it.
This archive was generated by hypermail 2.0.0 : Sun Jul 30 2006 - 09:14:15 EDT