[
https://issues.apache.org/jira/browse/OFBIZ-12365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre Smits updated OFBIZ-12365:
---------------------------------
Description:
With the introduction of bug fix under OFBIZ-5980, entities with a relationship
to the PartyRole entity (<relation rel-entity-name="PartyRole"> ) appear
erroneous (see error.log) when loading the definitions due to a foreign key
violation in the underlying dbms.
As an example:
{code:java}
SQL Exception while executing the following:
ALTER TABLE OFBIZ.AGREEMENT ADD CONSTRAINT AGRMNT_FPRTYRLE FOREIGN KEY
(PARTY_ID_FROM, ROLE_TYPE_ID_FROM) REFERENCES OFBIZ.PARTY_ROLE (PARTY_ID,
ROLE_TYPE_ID)
Error was: java.sql.SQLException: Constraint 'AGRMNT_FPRTYRLE' is invalid:
there is no unique or primary key constraint on table '"OFBIZ"."PARTY_ROLE"'
that matches the number and types of t$
java.sql.SQLException: Constraint 'AGRMNT_FPRTYRLE' is invalid: there is no
unique or primary key constraint on table '"OFBIZ"."PARTY_ROLE"' that matches
the number and types of the columns $
{code}
was:
With the introduction of bug fix under OFBIZ-5980, entities with a relationship
to the PartyRole entity (<relation rel-entity-name="PartyRole"> ) appear
erroneous when loading the definitions due to a foreign key violation in the
underlying dbms.
As an example:
{code:java}
SQL Exception while executing the following:
ALTER TABLE OFBIZ.AGREEMENT ADD CONSTRAINT AGRMNT_FPRTYRLE FOREIGN KEY
(PARTY_ID_FROM, ROLE_TYPE_ID_FROM) REFERENCES OFBIZ.PARTY_ROLE (PARTY_ID,
ROLE_TYPE_ID)
Error was: java.sql.SQLException: Constraint 'AGRMNT_FPRTYRLE' is invalid:
there is no unique or primary key constraint on table '"OFBIZ"."PARTY_ROLE"'
that matches the number and types of t$
java.sql.SQLException: Constraint 'AGRMNT_FPRTYRLE' is invalid: there is no
unique or primary key constraint on table '"OFBIZ"."PARTY_ROLE"' that matches
the number and types of the columns $
{code}
> Rel-entity error re PartyRole change
> ------------------------------------
>
> Key: OFBIZ-12365
> URL: https://issues.apache.org/jira/browse/OFBIZ-12365
> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Pierre Smits
> Priority: Major
>
> With the introduction of bug fix under OFBIZ-5980, entities with a
> relationship to the PartyRole entity (<relation rel-entity-name="PartyRole">
> ) appear erroneous (see error.log) when loading the definitions due to a
> foreign key violation in the underlying dbms.
> As an example:
> {code:java}
> SQL Exception while executing the following:
> ALTER TABLE OFBIZ.AGREEMENT ADD CONSTRAINT AGRMNT_FPRTYRLE FOREIGN KEY
> (PARTY_ID_FROM, ROLE_TYPE_ID_FROM) REFERENCES OFBIZ.PARTY_ROLE (PARTY_ID,
> ROLE_TYPE_ID)
> Error was: java.sql.SQLException: Constraint 'AGRMNT_FPRTYRLE' is invalid:
> there is no unique or primary key constraint on table '"OFBIZ"."PARTY_ROLE"'
> that matches the number and types of t$
> java.sql.SQLException: Constraint 'AGRMNT_FPRTYRLE' is invalid: there is no
> unique or primary key constraint on table '"OFBIZ"."PARTY_ROLE"' that matches
> the number and types of the columns $
> {code}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
