Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/UserGuide/JPA/Advanced JPA Development/Schema Generation/CascadeOnDelete"
< EclipseLink | UserGuide | JPA | Advanced JPA Development | Schema Generation
m |
|||
Line 27: | Line 27: | ||
|- | |- | ||
| OneToOne mapping | | OneToOne mapping | ||
− | | The related object is | + | | The deletion of the related object is cascaded on the database. This is only allowed for mappedBy/target-foriegn key OneToOne mappings (because of constraint direction). |
|- | |- | ||
| OneToMany mapping | | OneToMany mapping | ||
− | | The related objects | + | | The deletion of the related objects is cascaded on the database. |
|- | |- | ||
| ManyToMany mapping | | ManyToMany mapping | ||
− | | The join table is | + | | The deletion of the join table is cascaded on the database. (Target objects cannot be cascaded even if private because of constraint direction). |
|- | |- | ||
| DirectCollection | | DirectCollection | ||
− | | The direct table is | + | | The deletion of the direct table is cascaded on the database. |
|- | |- | ||
| AggregateCollection | | AggregateCollection | ||
− | | The aggregate table is | + | | The deletion of the aggregate table is cascaded on the database. |
|} | |} | ||
Revision as of 11:20, 1 February 2011
EclipseLink JPA
EclipseLink | |
Website | |
Download | |
Community | |
Mailing List • Forums • IRC • mattermost | |
Issues | |
Open • Help Wanted • Bug Day | |
Contribute | |
Browse Source |
Key API CascadeOnDelete
@CascadeOnDelete
>>>>>> THIS PAGE IS IN PROGRESS. PLEASE SEE DISCUSSION PAGE. <<<<<<
ON DELETE CASCADE is a database foreign key constraint option that automatically removes the dependent rows.
Use the @CascadeOnDelete annotation or the cascadeOnDelete property to specify that a delete operation performed on a database object is cascaded on secondary or related tables.
Performing a CascadeOnDelete on this object... | Does this... |
Entity | Defines that secondary or joined inheritance tables should cascade the delete on the database |
OneToOne mapping | The deletion of the related object is cascaded on the database. This is only allowed for mappedBy/target-foriegn key OneToOne mappings (because of constraint direction). |
OneToMany mapping | The deletion of the related objects is cascaded on the database. |
ManyToMany mapping | The deletion of the join table is cascaded on the database. (Target objects cannot be cascaded even if private because of constraint direction). |
DirectCollection | The deletion of the direct table is cascaded on the database. |
AggregateCollection | The deletion of the aggregate table is cascaded on the database. |
@Target(value={METHOD,FIELD,TYPE}) @Retention(value=RUNTIME) public @interface CascadeOnDelete
Configuration File
In the orm.xml descriptor file, specify cascade on delete as follows:
<source lang="xml"> <entity cascadeOnDelete="true"> <one-to-one cascadeOnDelete="true"> <one-to-many cascadeOnDelete="true"> <many-to-many cascadeOnDelete="true"> </source>