You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Milosz Tylenda (JIRA)" <ji...@apache.org> on 2008/12/21 13:02:44 UTC
[jira] Commented: (OPENJPA-557) Primary key sequences broken with
postgres schemas
[ 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.
Re: [jira] Commented: (OPENJPA-557) Primary key sequences broken with postgres schemas
Posted by Miłosz Tylenda <mt...@o2.pl>.
Hi Catalina,
The issue for schema handling is OPENJPA-842. As you will read, this turned out to be a more general problem, not specific to PostgreSQL.
Greetings,
Milosz
> Hi Milosz,
> I have committed your patch for this issue for future releases of 2.0 and
> 1.3.x.
> If you do need the patch be applied to 1.0.x, please reopen this issue.
>
> Please open separate JIRA issue as you uncover more problem with schema
> handling in PostgresSQL
>
> Thanks.
>
> Catalina Wei
>
> On Sun, Dec 21, 2008 at 4:02 AM, Milosz Tylenda (JIRA) wrote:
>
> >
> > [
> > 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.
> >
> >
>
Re: [jira] Commented: (OPENJPA-557) Primary key sequences broken with postgres schemas
Posted by catalina wei <ca...@gmail.com>.
Hi Milosz,
I have committed your patch for this issue for future releases of 2.0 and
1.3.x.
If you do need the patch be applied to 1.0.x, please reopen this issue.
Please open separate JIRA issue as you uncover more problem with schema
handling in PostgresSQL
Thanks.
Catalina Wei
On Sun, Dec 21, 2008 at 4:02 AM, Milosz Tylenda (JIRA) <ji...@apache.org>wrote:
>
> [
> 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.
>
>