DDC-731: Bi-directional cascade #900

New Issue

admin · 2026-01-22T12:54:37+01:00

admin commented

2026-01-22 12:54:37 +01:00

Originally created by @doctrinebot on GitHub (Aug 5, 2010).

Jira issue originally created by user jasper:

Example:

/****
 * @Entity
 */
class Foo {

[...]

/****
 * @OneToOne( targetEntity = "Bar", cascade = {"remove"} )
 * @JoinColumn( name = "bar_id", onDelete = "CASCADE" )
 */
protected $bar;

[...]

}

In this case, Doctrine should cascade whenever a Bar is deleted. But, when you delete a Foo, it will also cascade the other way around, resulting in also deleting the Bar corresponding to this Foo. A possible solution is unsetting $bar before you remove it in the EntityManager.

Originally created by @doctrinebot on GitHub (Aug 5, 2010). Jira issue originally created by user jasper: Example: ``` /**** * @Entity */ class Foo { [...] /**** * @OneToOne( targetEntity = "Bar", cascade = {"remove"} ) * @JoinColumn( name = "bar_id", onDelete = "CASCADE" ) */ protected $bar; [...] } ``` In this case, Doctrine should cascade whenever a Bar is deleted. But, when you delete a Foo, it will also cascade the other way around, resulting in also deleting the Bar corresponding to this Foo. A possible solution is unsetting $bar before you remove it in the EntityManager.

admin added the Bug label 2026-01-22 12:54:37 +01:00

admin closed this issue

2026-01-22 12:54:40 +01:00

admin commented

2026-01-22 12:54:42 +01:00

@doctrinebot commented on GitHub (Aug 5, 2010):

Comment created by @beberlei:

no, the mapping explicitly says If you delete Foo then also the Bar is deleted, i.e. {cascade="REMOVE"} leads to the behaviour Foo delete -> Bar delete.

@doctrinebot commented on GitHub (Aug 5, 2010): Comment created by @beberlei: no, the mapping explicitly says If you delete Foo then also the Bar is deleted, i.e. {cascade="REMOVE"} leads to the behaviour Foo delete -> Bar delete.

admin commented

2026-01-22 12:54:43 +01:00

@doctrinebot commented on GitHub (Aug 7, 2010):

Comment created by romanb:

You're using application-level and database-level cascades at the same time. This usually does not make sense. The behavior you describe is correct and is caused by the database foreign key constraint which is created with ON DELETE CASCADE.

@doctrinebot commented on GitHub (Aug 7, 2010): Comment created by romanb: You're using application-level and database-level cascades at the same time. This usually does not make sense. The behavior you describe is correct and is caused by the database foreign key constraint which is created with ON DELETE CASCADE.

admin commented

2026-01-22 12:54:44 +01:00

@doctrinebot commented on GitHub (Aug 7, 2010):

Issue was closed with resolution "Invalid"

@doctrinebot commented on GitHub (Aug 7, 2010): Issue was closed with resolution "Invalid"

admin referenced this issue

2026-01-22 16:02:04 +01:00

[PR #900] [MERGED] Fix connection mock fetchColumn signature #8868

admin referenced this issue

2026-01-22 16:02:05 +01:00

[PR #900] Fix connection mock fetchColumn signature #8872

Sign in to join this conversation.