Releases: prooph/event-store
Releases · prooph/event-store
6.0-beta.1 Release
This is a pre release for the upcoming changes in prooph/event-store v6 and related compontents.
The following list contains the most important changes. A detailed changelog will be added to the final v6 release.
5.1 Release
Added
- #94 It is now possible to ask the event store if it is in active transaction with
EventStore::isInTransaction(): bool
5.0 Release
Added
- Factories which help you set up the event store and related components
- the factories support
interop-container
for framework interoperability
- the factories support
- ConfigurableAggregateTranslator, see new documentation
- Package specific exceptions extending core exceptions
- Tons of tests
Changed
- event store now only requires
Prooph\Common\Messaging\Message
interface instead of domain event implementations - Nested transactions are marked as deprecated and will be removed with prooph/event-store 6
- Constructor signature of
AggregateRepository
, see #72 - Feature interface renamed to
Plugin
- If event store should perform a rollback but the used adapter does not support transactions an exception is thrown
- InMemoryAdapter is no longer used as the default adapter, you have to instantiate (or configure) the adapter you want to use
Removed
- ZF2 dependencies
PostCommitEvent
andPreCommitEvent
- now
Prooph\Common\Event\ActionEvent
s are triggered and you have to usegetParam
method to access for example all recorded events
- now
FeatureManager
the logic is now handled by theEventStoreFactory
Configuration
class, set up is handled by theEventStoreFactory
DomainEventMetadataWriter
asProoph\Common\Messaging\Message
s now providewithMetadata
andwithAddedMetadata
methods- DefaultAggregateTranslator in favour of the new ConfigurableAggregateTranslator
5.0-beta.3 Release
Third 5.0 beta release includes some bugfixes and 100 % test coverage
5.0-beta.2 Release
Second beta release.
An overview of all upcoming changes can be found here
5.0-beta.1 Release
Summary of changes can be found in #50
2.1.1 LTS Bugfix Release
Fixed
- #44 - Reset recorded events
We decided to provide LTS for prooph/event-store v2.x based on a request from @dottorbabba
thx again
4.0.1 Release
Fixed
- #44 - Recorded events are now reset before
EventStore.PostCommitEvent
is triggered
4.0 Release
Changed
- #42 adds support for nested transactions
This is a BC break because in versions < 4 an exception was thrown when EventStore::beginTransaction was called within an active transaction. Also event triggering was aligned:- EventStore.beginTransaction is triggered for each EventStore::beginTransaction call. The event provides two new parameters with information about the current transaction level: (bool)
isNestedTransaction
and (int)transactionLevel
- EventStore.commit.pre is triggered for each EventStore::commit call. It provides the same new parameters as the beginTransaction event
- EventStore.commit.post is only called once after all transactions of the current session are committed. Thus you can continue to attach a DomainEventDispatcher to this event to publish events after they are really committed to the database
- EventStore.beginTransaction is triggered for each EventStore::beginTransaction call. The event provides two new parameters with information about the current transaction level: (bool)
3.1 Release
Changed
- Support prooph/common 2.0