[DDC-1370] preInsert, postInsert, prePersist, postPersist, preUpdate, postUpdate code and documentation of events Created: 09/Sep/11 Updated: 26/Feb/14
|Project:||Doctrine 2 - ORM|
|Reporter:||Guilherme Blanco||Assignee:||Benjamin Eberlei|
Currently we have a set of Lifecycle events, but they seem to be misleading both in actual implementation and documentation.
One good example is prePersist and postPersist, which is only fired when you're creating new entities. It should be renamed to preInsert and postInsert.
But if we rename prePersist and postPersist to (pre|post)Insert, we may have a situation where you wanna cover both insert and update.
|Comment by Rafael Dohms [ 09/Sep/11 ]|
Also, documentation for post* methods is broken at the website:
"Changes in here are not relevant to the persistence in the database, but you can use this events to"
It cuts off in mid-sentence.
|Comment by Guilherme Blanco [ 09/Dec/11 ]|
RDohms, this paragraph was already sorted out.
The actual ticket is still valid here.
|Comment by Guilherme Blanco [ 20/Dec/11 ]|
Updating fix version
|Comment by Matt McNeill [ 26/Feb/14 ]|
Commenting here to say that this caused a lot of headaches for our project until we got it sorted out what these events really do.
The problem is that the term 'persist' is ambiguous - it means both persist and update in the context of the persist() function call, but only means INSERT in the context of the event system.