There was already a previous thread on this although I can't seem to find it off hand. I think some one was looking into it already so there might be a jira openned.
On Mon, May 04, 2009 at 09:53:41AM -0500, Michael Dick wrote: > Hi Martin, > > I think it's worth a JIRA (otherwise it'll get lost in the mail archive). > Off the top of my head I can't think of a reason why we'd need the sequence > table in this case, but maybe there's a use case that's eluding me (more > likely it's a bug). > > If you don't have a JIRA account let me know and I'll open the issue on your > behalf. > > -mike > > On Mon, May 4, 2009 at 8:24 AM, Martin Dirichs > <[email protected]>wrote: > > > > > Hi, > > > > using OpenJPA with all identity values generated by the datastore does not > > trigger the creation of OPENJPA_SEQUENCE_TABLE. However, as soon as a > > embeddable class is used, this table is being created although embeddable > > classes do not have a persistent identity on their own. > > > > At least this is the situation I get with a mapping that has all entities > > relying on generated values of GenerationType.IDENTITY. Introducing an > > embeddable class (mapped with @Embeddable, but not with @Entity) leads to > > the creation of OPENJPA_SEQUENCE_TABLE, which is unnecessary in my opinion. > > This wouldn't be a big deal per se, but it obstructs a quick check whether > > all identity fields are mapped correctly (as a correct mapping in my setup > > would not trigger creation of the sequence table). > > > > Is this issue worth a JIRA? > > > > Regards, > > Martin Dirichs. > > > > -- > > View this message in context: > > http://n2.nabble.com/OPENJPA_SEQUENCE_TABLE-created-unnecessarily-for-embeddable-classes-tp2787226p2787226.html > > Sent from the OpenJPA Users mailing list archive at Nabble.com. > > > > -- Ted Leung [email protected] The world is spinning too fast, it's making me dizzy.
