DDC-1443: Subscribers reachs maximum nesting level when creating association on pre/postPersist with cascade persist #2070

Open
doctrinebot opened this Issue Oct 20, 2011 · 4 comments

2 participants

@doctrinebot

Jira issue originally created by user @guilhermeblanco:

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.

@doctrinebot

Comment created by @guilhermeblanco:

Failing test case

@doctrinebot

Comment created by @guilhermeblanco:

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

@doctrinebot

Comment created by @beberlei:

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

@beberlei beberlei was assigned by doctrinebot Dec 6, 2015
@doctrinebot doctrinebot added the Bug label Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment