I've attached a simple maven project that demonstrates what might be a bug
in the way that OpenJPA handles cascading. However I freely admit of the
strong possibility that instead I'm just being stupid. That's why I'm
coming to the user list first.
Please find attached a JPA project that describ
The difference in timing is that when I am not doing the query on the joined
field I can insert 2500 new entities in about 20 seconds but when I add the
new function that looks up he joined field and inserts it, the same process
and data takes about 30 minutes.
Basically my code works like this
Is there any way I can force OpenJPA 1.2.1 to use a specific index when
querying? My field is indexed but key lookups are lightning fast whereas if
I query to search on a non-key field which is indexed it takes forever, so I
am assuming that it is not using the index. It may be an issue with the
Hmm but shouldn't the list server handle that? Maybe I'll re-subscribe and
see if it fixes it.
-Original Message-
From: Daryl Stultz [mailto:da...@6degrees.com]
Sent: Saturday, 3 October 2009 6:12 AM
To: users@openjpa.apache.org
Subject: Re: Result limit
On Fri, Oct 2, 2009 at 3:38 PM, C
