jpa - Why EclipseLink is adding discriminator column for joined inheritance strategy? -


i using joined inheritance strategy eclipselink jpa implementation. have noticed eclipselink adding discriminator column, named default dtype, database schema. understand, discriminator needed 1 table inheritance strategy, why joined strategy?

eclipselink needs column because i've got errors after removing it. column added performance reasons, etc? not particularly happy since point of view of database schema column unnecessary clutter.

hibernate based jpa not similar.

from joined table inheritance:

in joined table inheritance, each class shares data root table. in addition, each subclass defines own table adds extended state. following example shows 2 tables, project , l_project, 2 classes, project , largeproject:

...

the discriminator column determines type , joined table use need discriminator column in parent table.


Comments

Popular posts from this blog

unicode - Are email addresses allowed to contain non-alphanumeric characters? -

C#: Application without a window or taskbar item (background app) that can still use Console.WriteLine() -

c++ - Convert big endian to little endian when reading from a binary file -