openjpa-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject Re: Problems with Oracle 11g and primary_key as rowtype IDENTITY
Date Sun, 02 Oct 2011 17:29:15 GMT
The guys from Oracle do (a bit offensive) argue that for such reasons
sequences do exist.

"Oracle has *sequences* for this purpose.
They are either directly used in an INSERT statement, or assigned to a
column by means of a *trigger*.."

So my question might be: Why does openJPA not create sequences? Am I missing
some param in my config?
I have seen for MySQL there is an additional "sequence-table" created with
all index. In Oracle there seems to be no such table ... while except the
persistance.xml the code is 1:1 the same.


2011/10/1 <>

> Hi,
> when using Oracle 11g with openJPA I do get the following warning while the
> tables are populated by openJPA:
> "Oracle" does not support auto-assigne d column values.  The column may not
> behave as desired.
> ... and the effect is obviously that, as soon as you try to add a new
> column with a null value for a primary key, Oracle will throw an
> Exception...
> I can read from the Issue tracker:
> But actually the JIRA Issue 1090 is about adding this warning, not about
> how to solve it.
> What is actually the solution to fix it?
> Is it database related or do we need to change our code?
> Thank you!
> Sebastian
> --
> Sebastian Wagner

Sebastian Wagner

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