Signal/Slot adapter for persistence events
|Status:||Under Review||Start date:||2012-06-19|
|Priority:||Could have||Due date:|
|Assignee:||Adrian Föder||% Done:||
Doctrine offers the so-called "lifecycle" events that are emitted on various stages in the life of an entity. I'd suggest to provide an Interface/Implementation pair for FLOW3 that translates these events to FLOW3 signals.
At the first draft, the implementation would of course handle Doctrine events.
My question to start with is, what "events" should that cover, initially? As a reminder; Doctrine offers
Do we need to cover all these events? We should regard that not all backends offer exact equivalents, so we should agree to some common denominator.
Updated by Adrian Föder 11 months ago
OK, so far I would go for the following signals:
while looking around for some ideas, I discovered the Generic\Backend\AbstractBackend's methods, having emitRemovedObject() and emitPersistedObject(), whereas the latter additionally sends the state of the object: OBJECTSTATE_RECONSTITUTED or OBJECTSTATE_NEW.
This could be also adapted to that Persistence Signal Emitter, but mustn't. Consider this as a note only.
Updated by Gerrit Code Review 11 months ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/12210