openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Sutter <>
Subject Re: OpenJPA 2.2.0 , Oracle Issue
Date Mon, 04 Feb 2013 22:20:10 GMT
The @ForeignKey annotation is helpful for specifying foreign keys in
certain scenarios.  But, I'm surprised that this annotation would be
required for Oracle and not Postgres.  The basic metadata retrieval from
the database should be very similar.  But, I know how it is...  If you can
make progress with the @ForeignKey annotation, then do it and move on...

But, if you have the cycles to isolate this issue via a testcase and open a
JIRA, it would be of great help to our community.


On Sat, Feb 2, 2013 at 10:29 AM, sudhi <>wrote:

> By using @ForeignKey annotation from OpenJPA over relational dependencies
> seems to work fine.
> But this is not right approach, makes the application dependent on the
> provider. Seems this is a bug in OpenJPA when oracle is used as it worked
> fine when Postgres was used (without @ForeignKey).
> --
> View this message in context:
> Sent from the OpenJPA Developers mailing list archive at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message