There's no common definition for "shared primary key" that I'm aware of.
But let's just go and create a definition that might make sense and
see how JPA would deal with it.
If two tables have the same type of primary key, and some values of
one table's PK are also values of another table's
Would you say that the following statement is accurate or not?
"The JPA specification doesn't have a way to deal with a shared primary
key."
Isn't this what "secondary-table" addresses? Are there other strategies
that apply to this?
Hi,
You're getting an error because optional is set to false - try setting it to
true or removing it from the @OneToOne annotation.
-mike
On Fri, Jul 16, 2010 at 2:45 PM, Rajeev Chaudhary wrote:
>
> How can I prevent A child in one-to-one getting persisted/merge. I only
> want
> to fetch the ch
How can I prevent A child in one-to-one getting persisted/merge. I only want
to fetch the child information. When I am persisting FacPersonDto, I get
error, saying the relation expects a value for the id. currently it is null.
I also tried making updatabale, insertable = false in
@JoinColumn(name=
Russell Collins wrote:
>
>
> You should have
>
> SELECT b.a_id FROM B where B.id = 123
>
>
>From what you said I think that you mix two different things: JPQL and SQL
--
View this message in context:
http://openjpa.208410.n2.nabble.com/Unnecesery-INNER-JOIN-tp5297321p5303473.html
Sent fro
Hi Jerry and Harald,
It's always good to hear positive remarks about our OpenJPA efforts...
Besides Jerry's useful experiences, the other thing to point out is that you
should be able to extend the OpenJPA implementation to use the PostGIS
features more directly (vs native queries). But, this wou
I've been walking down the same road. I'm also working with PostGIS. I
started with Hibernate and then shifted to OpenJPA and haven't looked back.
I am using the NativeQuery mechanism. I had an exchange with Pinaki regarding
the Critera API which was added to JPA 2.0 some number of weeks bac
I'm currently evaluating OpenJPA as a replacement for Hibernate. I'm rather
frustrated by the lack of JPA 2.0 compliance in Hibernate, and I'm glad to
say I haven't run into any such problems with OpenJPA so far.
On the other hand, there are some extensions beyond the scope of JPA which
work with
In other words, instead of saying this
SELECT b.a.id FROM B where B.id = 123
You should have
SELECT b.a_id FROM B where B.id = 123
-Original Message-
From: Russell Collins [mailto:russell.coll...@mclaneat.com]
Sent: Friday, July 16, 2010 9:08 AM
To: 'users@openjpa.apache.org'
Subject: R
I guess what I am saying is that this join is necessary. In standard SQL the
only way you are going to get relational data from two tables is by joining the
tables or performing nested selects. I think the thing you want to do is to
just look for the column on table "B" that corresponds to th
Just your normal JVM memory constraints... :-)
Seriously, is there no defined maximum. But, the size of the cache needs to
be experimented with. Just making the cache larger doesn't necessarily make
things run faster. At a certain point, depending on your application, you
will reach a point of
Thanks, one more question about data cache. Is there a limit on the maximum
CacheSize on a single JVM?
Thanks
> http://ehcache.org/documentation/openjpa_provider.html
>
> On Wed, Jul 14, 2010 at 9:09 PM, Rick Curtis wrote:
>
>> This is something that I've always wanted to experiment with,
12 matches
Mail list logo