It would be nice to fix this. I'd hate to see anyone else hit this. Failing that documenting this unexpected behavior would be okay.
-=- Jerry (via iPhone) On Jun 9, 2010, at 12:38 AM, "Christopher Schmidt-4 [via OpenJPA]" <ml-node+5156733-944799821-93...@n2.nabble.com > wrote: > Jersey, > > You are right. I changed the sequenceName to xxx and it works... > > Thx for help :) > > Am 08.06.2010 23:17 schrieb "Jeremy Bauer" <[hidden email]>: > > Hi Christopher, > > As it turns out, I don't think this problem is the same as > OPENJPA-1259. > There is special code in the PostgresDictionary that treats sequences > suffixed with "_SEQ" as system managed sequences. The comment in > PostgresDictionary.isSystemSequence reads: > > // filter out generated sequences used for bigserial cols, > which are > // of the form <table>_<col>_seq > > This explains why the same code worked for me on DB2. Are you able to > modify the sequence name? (ex. sequenceName = "seq_obj_item_id") > If not, > please file a new JIRA. It may/should be possible to make the code > a bit > smarter by actually verifying _seq suffixed sequences are for a > bigserial > column[1] instead of just making the assumption. > > -Jeremy > > [1] > http://www.postgresql.org/docs/8.4/static/datatype-numeric.html#DATATYPE-SERIAL > > > On Mon, Jun 7, 2010 at 2:39 PM, Jeremy Bauer <[hidden email]> wrote: > > > Christopher, > > > > I am ... > > > View message @ > http://openjpa.208410.n2.nabble.com/relation-mySequence-already-exists-tp5136569p5156733.html > To start a new topic under OpenJPA Users, email > ml-node+208411-1595610943-93...@n2.nabble.com > To unsubscribe from OpenJPA Users, click here. > -- View this message in context: http://openjpa.208410.n2.nabble.com/relation-mySequence-already-exists-tp5136569p5157786.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
