-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PostLoad event on fetch joined entities - Lifecycle Callback not firing #6568
Comments
Any load operation should trigger postLoad events, so this is a bug. Can
you submit a test case to be added to our test suite?
…On 21 Jul 2017 09:28, "stoccc" ***@***.***> wrote:
I have a problem with a Lifecycle Callback of Doctrine ORM
<http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/events.html#lifecycle-callbacks>:
the callback is not executed on fetch-joined entities, while it's regularly
executed on entities that are lazy-loaded.
Is there a bug in the ObjectHydrator, or it is a lack of documentation
about that?
See this question on stackoverflow
<https://stackoverflow.com/questions/45211316/doctrine-postload-lifecycle-callback-not-executed-in-fetchjoin>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6568>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJakNngALqVjHN9rC7paj5DntVTSGtVks5sQFMigaJpZM4OfDYL>
.
|
I'm not so expert, I hope I did the right thing! |
@stoccc test looks good, thanks! |
@Ocramius The problem was in my application, I was using in PostLoad of the root entity some informations setted in PostLoad of the fetchjoined entities, but certainly no one can guarantee me that one PostLoad is executed before or after some other PostLoad. I close, thanks for your time. |
I have a problem with a Lifecycle Callback of Doctrine ORM: the callback is not executed on fetch-joined entities, while it's regularly executed on entities that are lazy-loaded.
Is there a bug in the ObjectHydrator, or it is a lack of documentation about that?
See this question on stackoverflow
The text was updated successfully, but these errors were encountered: