[
https://issues.apache.org/jira/browse/OPENJPA-2022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13820399#comment-13820399
]
Jason Zwolak commented on OPENJPA-2022:
---------------------------------------
I'm also having this same issue in 2.2.2, 2.2.0, 2.1.1, and 2.3.0-snapshot (Oct
24th, 2013).
Here's the DDL and the OpenJPA generated schema.xml for one table (this
schema.xml was generated with the 2.3.0 snapshot, but I'm pretty sure it looks
identical for 2.2.2, 2.2.0, and 2.1.1).
SCHEMA:
{code}
<table name="MODELS">
<column name="MODEL_ID" type="decimal" type-name="NUMBER"
not-null="true" size="22"/>
<column name="MODEL_DESCRIPTION" type="varchar"
type-name="VARCHAR2" not-null="true" size="240"/>
<column name="PERSON_ID" type="decimal" type-name="NUMBER"
not-null="true" size="22"/>
<column name="VERSION_NUM" type="decimal" type-name="NUMBER"
size="22"/>
<column name="VERSION_DESC" type="varchar" type-name="VARCHAR2"
size="80"/>
<column name="VERSION_DATE" type="timestamp" type-name="DATE"
default="sysdate" size="7"/>
<column name="LOCK_FLAG" type="varchar" type-name="VARCHAR2"
size="1"/>
<column name="BASE_MODEL_ID" type="decimal" type-name="NUMBER"
size="22"/>
<column name="PRIVATE_FLAG" type="varchar" type-name="VARCHAR2"
size="1"/>
<column name="SECURITY_LEVEL" type="decimal" type-name="NUMBER"
size="22"/>
<column name="LAST_MODIFIED" type="timestamp"
type-name="TIMESTAMP(6)" default="sysdate" size="11" decimal-digits="6"/>
<fk name="MODL_MODL_FK" delete-action="restrict"
to-table="PROCESSDB_DEV.MODELS" column="BASE_MODEL_ID"/>
<fk name="MODL_PERS_FK" delete-action="restrict"
to-table="PROCESSDB_DEV.PERSONS" column="PERSON_ID"/>
<index name="MODL_PERS_FK_I" column="PERSON_ID"/>
<index name="MODL_PK" unique="true" column="MODEL_ID"/>
</table>
{code}
DDL:
{code}
CREATE TABLE "PROCESSDB_DEV"."MODELS"
( "MODEL_ID" NUMBER NOT NULL ENABLE,
"MODEL_DESCRIPTION" VARCHAR2(240 BYTE) NOT NULL ENABLE,
"PERSON_ID" NUMBER NOT NULL ENABLE,
"VERSION_NUM" NUMBER,
"VERSION_DESC" VARCHAR2(80 BYTE),
"VERSION_DATE" DATE DEFAULT sysdate,
"LOCK_FLAG" VARCHAR2(1 BYTE),
"BASE_MODEL_ID" NUMBER,
"PRIVATE_FLAG" VARCHAR2(1 BYTE),
"SECURITY_LEVEL" NUMBER,
"LAST_MODIFIED" TIMESTAMP (6) DEFAULT sysdate,
CONSTRAINT "MODL_PK" PRIMARY KEY ("MODEL_ID")
USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 131072 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE
DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "USERS" ENABLE,
CONSTRAINT "MODL_MODL_FK" FOREIGN KEY ("BASE_MODEL_ID")
REFERENCES "PROCESSDB_DEV"."MODELS" ("MODEL_ID") ENABLE NOVALIDATE,
CONSTRAINT "MODL_PERS_FK" FOREIGN KEY ("PERSON_ID")
REFERENCES "PROCESSDB_DEV"."PERSONS" ("PERSON_ID") ENABLE NOVALIDATE
) SEGMENT CREATION IMMEDIATE
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 131072 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE
DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "USERS" ;
CREATE INDEX "PROCESSDB_DEV"."MODL_PERS_FK_I" ON "PROCESSDB_DEV"."MODELS"
("PERSON_ID")
PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS
STORAGE(INITIAL 131072 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE
DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "USERS" ;
{code}
> Reversemappingtooltask with oracle is failing like in OPENJPA-1940 previous
> bug
> -------------------------------------------------------------------------------
>
> Key: OPENJPA-2022
> URL: https://issues.apache.org/jira/browse/OPENJPA-2022
> Project: OpenJPA
> Issue Type: Bug
> Components: tooling
> Affects Versions: 2.1.0, 2.1.1, 2.2.0
> Environment: Woking on a windows pc with a oracle 10g express
> database, eclipse helios, using oracle 11.2.0.2 driver.
> Reporter: sebastien morissette
> Assignee: Michael Dick
> Fix For: 2.4.0
>
>
> When running either of the versions of the reversemappingtool as reported in
> the 1940 bug as fixed, i get the same error as in 2.1.0 :
> [reversemappingtool] 2363 openjpa INFO [main] openjpa.Tool -
> ReverseMappingTool : generating classes.
> [reversemappingtool] 2365 openjpa INFO [main] openjpa.MetaData - Table
> "RMTOOLS."AppUsers"" could not be reverse mapped. This means that the table
> does not have a primary key (primary keys are required to establish unique
> identifiers for all persistent objects) and does not match a known pattern
> for a table used for cross-reference or value collections.
> [reversemappingtool] 2366 openjpa INFO [main] openjpa.MetaData - Table
> "RMTOOLS."CredentialTypes"" could not be reverse mapped. This means that the
> table does not have a primary key (primary keys are required to establish
> unique identifiers for all persistent objects) and does not match a known
> pattern for a table used for cross-reference or value collections.
> [reversemappingtool] 2366 openjpa INFO [main] openjpa.MetaData - Table
> "RMTOOLS."Credentials"" could not be reverse mapped. This means that the
> table does not have a primary key (primary keys are required to establish
> unique identifiers for all persistent objects) and does not match a known
> pattern for a table used for cross-reference or value collections.
> this happens for all my tables. Is it possible this bug was reintroduced?
> thanks
--
This message was sent by Atlassian JIRA
(v6.1#6144)
