Additional information for issue #2
Let's check what is referential integrity in the database:
Referential integrity is a property of data stating references within it are valid. In the context of relational databases, it requires every value of one attribute (column) of a relation (table) to exist as a value of another attribute (column) in a different (or the same) relation (table).
For referential integrity to hold in a relational database, any column in a base table that is declared a foreign key can contain either a null value, or only values from a parent table's primary key or a candidate key. In other words, when a foreign key value is used it must reference a valid, existing primary key in the parent table.
In my case:
Parent table it is table with PZINSKEY.
Child table it is table with PXINSINDEXEDKEY + reference to Parent table on column PZINSKEY.
But this reference can't be validated by database, because record does not exists in Parent table
when Pega do insert record into Child table.
Insert record into PARENT/MASTER table (work table)
and then Insert record into CHILD table (idx work table)
Is it property of Pega engine: insert record into IDX table, and then insert into PARENT table?
How to change this order in the Pega?
Posted: 3 years ago
Posted: 6 Oct 2017 15:24 EDT
Jim Kelly (JimKelly_GCS)
Principal Software Solutions Engineer
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page.
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
We have also sent you a private message opening up a communication channel in case you have any further questions.