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