[
https://issues.apache.org/jira/browse/OPENJPA-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658381#action_12658381
]
Milosz Tylenda commented on OPENJPA-557:
----------------------------------------
Applying the patch and running the test suite reveals another problem with
schema handling in PostgreSQL. I will open a separate JIRA issue.
> 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
> Attachments: OPENJPA-557.patch
>
>
> 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.
