[
https://issues.apache.org/jira/browse/OPENJPA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649089#action_12649089
]
Michal Borowiecki commented on OPENJPA-557:
-------------------------------------------
I experienced this bug in geronimo 2.1.3
I checked out openjpa tag 1.0.3 sources, applied the patch, compiled and
substituted the class file in openjpa-1.0.3.jar in geronimo 2.1.3 repository.
I confirm the patch works.
This issue is very important and I hope someone applies it to trunk soon :)
Thanks for the patch Roger!
> Primary key sequences broken with postgres schemas
> --------------------------------------------------
>
> Key: OPENJPA-557
> URL: https://issues.apache.org/jira/browse/OPENJPA-557
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.0.2
> Reporter: Roger Keays
>
> as per http://www.nabble.com/forum/ViewPost.jtp?post=15460899&framed=y
> OpenJPA issues a SELECT currval('user_id_seq'); query to get the current PK
> value on postgres. This should *not* execute correctly when using a schema.
> The correct query is SELECT currval('schemaname.user_id_seq');
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
