mirror of
https://github.com/doctrine/orm.git
synced 2026-03-24 06:52:09 +01:00
DDC-73: Lifecycle Events only work with undocumented @HasLifecycleCallbacks in Annonation classes #84
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doctrinebot on GitHub (Oct 29, 2009).
Jira issue originally created by user nicokaiser:
When using Docblock Annotations, Lifecycle Events don't work as described here:
http://www.doctrine-project.org/documentation/manual/2_0/en/events
Functions with e.g. "@PrePersist" annonations are not called unless the class(!) has "@HasLifecycleCallbacks" annotation in its class header docblock.
This behavior should be either documented or changed (no need for the @HasLifecycleCallbacks annotation)
@doctrinebot commented on GitHub (Nov 6, 2009):
Comment created by lucasts:
Working patch to trunk(r6683)
WIth this patch the foreach ran every time, but as metadata are cached, I guess that will not be a problem.
@doctrinebot commented on GitHub (Nov 7, 2009):
Comment created by romanb:
This should rather be fixed in the documentation instead. I think @HasLifecycleCallbacks is useful not only to save some overhead but also as a visual clue to quickly see whether a class has lifecycle callbacks without looking at all methods.
@doctrinebot commented on GitHub (Nov 7, 2009):
Comment created by @guilhermeblanco:
I think the opposite.
Overhead will only exist during metadata creation.
It's then irrelevant since we strongly suggest a cache mechanism at the top of metadata information.
I'm +1 to commit suggested patch.
@doctrinebot commented on GitHub (Nov 7, 2009):
Comment created by romanb:
Its far from irrelevant. Everything should be as fast as possible and during development you usually dont use APC/memcache as metadata cache because you would have to clear it manually after every change. Its simply not worth this absolutely minor convenience that we iterate over *all* methods of all entity classes just to look for lifecycle callbacks.
Again, this needs to be fixed in the documentation.
@doctrinebot commented on GitHub (Nov 7, 2009):
Comment created by romanb:
And to make it even clearer: Not even a metadata cache is the ultimate thing for performance since the unserialization is not very fast either. So please dont ever think something is irrelevant. This is php and php is pretty slow.
@doctrinebot commented on GitHub (Nov 8, 2009):
Issue was closed with resolution "Fixed"
@doctrinebot commented on GitHub (Dec 13, 2015):
Imported 1 attachments from Jira into https://gist.github.com/359f27d0bca83a98357d