users@glassfish.java.net

Re: Two entity classes mapped to same table

From: <glassfish_at_javadesktop.org>
Date: Fri, 18 May 2007 13:16:02 PDT

Hi Markus,

EntityClassB and EntityClassC only share the primary key. Actually, they also share a version field that is automatically updated when we do an update (not by the container, but by the database). That version field is probably what is causing the problem.

We need to have two classes mapped to the same table because this is a legacy table that was not modelled according to how we are using the data.

Andrew
[Message sent by forum member 'asmithgf' (asmithgf)]

http://forums.java.net/jive/thread.jspa?messageID=217908