Doctrine 2 - ORM

Subscribers reachs maximum nesting level when creating association on pre/postPersist with cascade persist

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: Git Master
  • Fix Version/s: None
  • Component/s: ORM
  • Security Level: All
  • Labels:
    None

Description

Suppose a situation where:

A -> B

Where the OneToOne unidirectional association contains cascade persist.

If I decide to save an entity B that should create an A instance, it goes into maximum nesting level no matter if I track prePersist or postPersist.

  1. File
    DDC1443Test.php
    20/Oct/11 8:10 PM
    4 kB
    Guilherme Blanco
  2. File
    DDC1443Test.php
    20/Oct/11 6:54 PM
    3 kB
    Guilherme Blanco

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Benjamin Eberlei added a comment -

Ah yes, this never worked. The transaction stuff will fix that. You have to use scheduleForInsert() something inside prePersist.

Show
Benjamin Eberlei added a comment - Ah yes, this never worked. The transaction stuff will fix that. You have to use scheduleForInsert() something inside prePersist.
Hide
Permalink
Guilherme Blanco added a comment -

Uploading a new version, now passing successfully, but consuming the onFlush event (which should not be ideal).

Show
Guilherme Blanco added a comment - Uploading a new version, now passing successfully, but consuming the onFlush event (which should not be ideal).
Hide
Permalink
Guilherme Blanco added a comment -

Failing test case

Show
Guilherme Blanco added a comment - Failing test case

People

  • Assignee:
    Benjamin Eberlei
    Reporter:
    Guilherme Blanco
Vote (0)
Watch (1)

Dates

  • Created:
    Updated: