Just a quick apology up-front because I haven't had time to follow up my problem
myself. I fully intend to at some point soon, but in the meantime, I am having
problems with cascading inserts, which I think may be closely related, so I
thought I'd add it into this thread.
I create a child and
Thanks guys, I put @Inheritance(strategy=InheritanceType.TABLE_PER_CLASS) to
AbstractFoo and now it works fine...I have also put
@Inheritance(strategy=InheritanceType.TABLE_PER_CLASS) to the first concrete
class of my class hierarchy otherwise the SINGLE_TABLE strategy is used for
the branch.
You are right. OpenJPA should use the inheritance strategy used at the root
of the hierarchy throughout the derived tree. The extra strategy
specification perhaps is resulting from the facility to support mixed
strategy. Needs further investigation...
hallmit wrote:
>
> Thanks guys, I put @Inhe
I am building out an object model and services for an existing relational
model and the table structure is a little strange and I am having trouble
with the object mapping.
Here are the details
We have 2 tables
company with primary key
id
12M_company_venue with columns
parent_company_id
venue_co
This mixed strategy can be very usefull. But obviously there is
uncompatibility with standards. I think that additional annotation can
be used to change standard behaviour. So, at this example strict
TABLE_PER_CLASS strategy should work without any additional annotations.
And to get the mixed s
I am attempting to load all the persistent class metadata eagerly. I
realize this isn't great performance-wise, but I need to do it for the
time-being. I had wanted to call:
ClassMetaData[] classMetaDatas =
conf.getMetaDataRepositoryInstance().getMetaDatas();
but realized the dat
Hi Serge,
Could you please open a JIRA so we can track this issue?
Thanks,
Craig
On May 11, 2009, at 11:03 AM, Serge Bogatyrev wrote:
This mixed strategy can be very usefull. But obviously there is
uncompatibility with standards. I think that additional annotation
can be used to change st
