Feature #38177

Signal/Slot adapter for persistence events

Added by Adrian Föder over 9 years ago. Updated over 8 years ago.

Status:
Rejected
Priority:
Could have
Assignee:
Category:
Persistence
Target version:
-
Start date:
2012-06-19
Due date:
% Done:

0%

Estimated time:
PHP Version:
Has patch:
No
Complexity:

Description

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

  • preRemove
  • postRemove
  • prePersist
  • postPersist
  • preUpdate
  • postUpdate
  • postLoad
  • loadClassMetadata
  • preFlush
  • onFlush
  • postFlush
  • onClear

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.


Related issues

Related to TYPO3.Flow - Feature #47228: Allow doctrine event listeners to be configuredResolvedAlexander Berl2013-04-15

Actions

Also available in: Atom PDF