Atomic Operation is failing to update child entities with FK integrity constraint violation #3322
Description
I have following 2 entities where in database decision's ID is a FK in legal table.
package com.example.app.model;
import jakarta.persistence.*;
import lombok.Getter;
import lombok.Setter;
import java.util.ArrayList;
import java.util.List;
@Entity
@Getter
@Setter
public class Decision {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
private String type;
private String outcome;
@OneToMany(mappedBy = "decision", cascade = CascadeType.ALL, orphanRemoval = true)
private List<Legal> legalList = new ArrayList<>();
}
and
package com.example.app.model;
import jakarta.persistence.*;
import lombok.Getter;
import lombok.Setter;
@Entity
@Getter
@Setter
public class Legal {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
private Long id;
private String name;
@ManyToOne
@JoinColumn(name = "decision_id", nullable = false)
private Decision decision;
}
Since I want to use atomic operation to update decision along with list of associated legal lists, I tried the following sample request but its failing saying integrity constraint violated FK - parent key not found.
{
"atomic:operations": [
{
"op": "add",
"data": {
"type": "decision",
"lid": "temp-decision-1",
"attributes": {
"type": "Court Decision",
"outcome": "Approved"
}
}
},
{
"op": "add",
"data": {
"type": "legal",
"attributes": {
"name": "Legal Document 1"
},
"relationships": {
"decision": {
"data": {
"type": "decision",
"id": "temp-decision-1"
}
}
}
}
}
]
}
I am getting Database Error - integrity constraint violated - parent key not found.
Observations
• Issue with Foreign Key Constraint:
• It seems that Elide replaces the client-generated ID (temp-decision-1) with an auto-generated ID while persisting Decision.
• When it attempts to insert Legal, it fails because the referenced decision_id (temp-decision-1) is not found in the database.
• Possible Root Cause:
• Elide might be executing both operations simultaneously instead of ensuring Decision is persisted first and then inserting Legal.
• Since Decision.id is auto-generated, Elide cannot resolve the temporary ID correctly before Legal is inserted.
Expected Behavior
• The Decision should be persisted first, generating a valid id.
• The Legal entity should then reference the newly created Decision using the correct id.
• The entire request should execute atomically, ensuring all operations succeed or fail together.
Questions
1. Does Elide guarantee sequential execution in atomic operations (ensuring Decision is persisted first before inserting Legal)?
2. How can I ensure that Legal correctly references the generated Decision.id instead of a temporary client-assigned ID?
3. Is there an alternative way to enforce foreign key constraints while using Atomic Operations in Elide?
Environment Details
• Elide Version: 7.1.4
• Database Used: Oracle
• Spring Boot Version: 3.3.7