openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Teresa Kan (JIRA)" <>
Subject [jira] Updated: (OPENJPA-399) openjpa did not handle multiple schema names with same table name
Date Thu, 11 Oct 2007 21:40:51 GMT


Teresa Kan updated OPENJPA-399:

    Attachment: OPENJPA_399_2.patch

attach 2nd patch and test case:
1) I removed the NativeJDBCSeq code since it worked as design.
2) Include the documentation changes in the OpenJPA manaual and Ref guide
3) inlcude the test case

> openjpa did not handle multiple schema names with same table name
> -----------------------------------------------------------------
>                 Key: OPENJPA-399
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.0.1
>         Environment: JDK1.5, OPENJPA verison 580425
>            Reporter: Teresa Kan
>         Attachments: OPENJPA_399.patch, OPENJPA_399_2.patch
> Two entities have the same table name but with different schema, only one table is created.
In addition, when two entities use the generatedType.AUTO for ID, only one OPENJPA_SEQUENCE-TABLE
is created.
> The problem due to the SchemaGroup.findTable() which only looked for a table name from
all the schemas. Once the table was found in one of the schema then it exited and assumed
that the table existed. Same problem in the TableJDBCSeq.addSchema().

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message