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:10:44 UTC
[jira] Created: (OPENJPA-842) Schema handling in PostgreSQL
Schema handling in PostgreSQL
-----------------------------
Key: OPENJPA-842
URL: https://issues.apache.org/jira/browse/OPENJPA-842
Project: OpenJPA
Issue Type: Bug
Components: jdbc
Affects Versions: 2.0.0
Environment: PostgreSQL 8.3
Reporter: Milosz Tylenda
Priority: Minor
Schema tool gets confused in a situation where it checks for existence of some table without schema but the same table already exists in some schema.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (OPENJPA-842) Handling of default schema
Posted by "Milosz Tylenda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Milosz Tylenda updated OPENJPA-842:
-----------------------------------
Environment: PostgreSQL 8.3, DB2 9.1 (was: PostgreSQL 8.3)
Summary: Handling of default schema (was: Schema handling in PostgreSQL)
Changed the issue summary as the issue is not PostgreSQL-specific.
> Handling of default schema
> --------------------------
>
> Key: OPENJPA-842
> URL: https://issues.apache.org/jira/browse/OPENJPA-842
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.0.0
> Environment: PostgreSQL 8.3, DB2 9.1
> Reporter: Milosz Tylenda
> Priority: Minor
>
> Schema tool gets confused in a situation where it checks for existence of some table without schema but the same table already exists in some schema.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-842) Schema handling in PostgreSQL
Posted by "Milosz Tylenda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658484#action_12658484 ]
Milosz Tylenda commented on OPENJPA-842:
----------------------------------------
I forgot about one thing. The steps should be:
1. Run the mentioned test or do this Sunday thing.
2. Drop non-schema table openjpa_sequence_table, i.e. the openjpa_sequence_table in public schema.
3. Run the test suite.
> Schema handling in PostgreSQL
> -----------------------------
>
> Key: OPENJPA-842
> URL: https://issues.apache.org/jira/browse/OPENJPA-842
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.0.0
> Environment: PostgreSQL 8.3
> Reporter: Milosz Tylenda
> Priority: Minor
>
> Schema tool gets confused in a situation where it checks for existence of some table without schema but the same table already exists in some schema.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-842) Schema handling in PostgreSQL
Posted by "Milosz Tylenda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658382#action_12658382 ]
Milosz Tylenda commented on OPENJPA-842:
----------------------------------------
This can be reproduced by running the test case from OPENJPA-557 or by creating manually something like this against PostgreSQL:
create schema sunday;
create table sunday.openjpa_sequence_table(v int);
Then, if you run the test suite, plenty of test cases will fail.
> Schema handling in PostgreSQL
> -----------------------------
>
> Key: OPENJPA-842
> URL: https://issues.apache.org/jira/browse/OPENJPA-842
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.0.0
> Environment: PostgreSQL 8.3
> Reporter: Milosz Tylenda
> Priority: Minor
>
> Schema tool gets confused in a situation where it checks for existence of some table without schema but the same table already exists in some schema.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (OPENJPA-842) Schema handling in PostgreSQL
Posted by "Milosz Tylenda (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENJPA-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12658505#action_12658505 ]
Milosz Tylenda commented on OPENJPA-842:
----------------------------------------
It looks like a known issue - see comment in SchemaGroup.findTable(Schema, String) [1].
The same scenario is reproducible in DB2 also.
[1] http://fisheye6.atlassian.com/browse/openjpa/trunk/openjpa-jdbc/src/main/java/org/apache/openjpa/jdbc/schema/SchemaGroup.java?r=584330#l190
> Schema handling in PostgreSQL
> -----------------------------
>
> Key: OPENJPA-842
> URL: https://issues.apache.org/jira/browse/OPENJPA-842
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.0.0
> Environment: PostgreSQL 8.3
> Reporter: Milosz Tylenda
> Priority: Minor
>
> Schema tool gets confused in a situation where it checks for existence of some table without schema but the same table already exists in some schema.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.