Skip to content

Conversation

schauder
Copy link
Contributor

This change enables the manipulation of the DbChange instance before it gets interpreted and turned into SQL statements.

Only for Aggregate Roots events get fired, since these are the abstraction the repositories work on.
Insert and Update events got removed since this distinction doesn't exist on the Aggregate Root level.
It only exists on the level of entities and/or tables which is represented by DbActions.

Improved some tests to properly check all the events triggered.

Issue: https://jira.spring.io/browse/DATAJDBC-120

This change enables the manipulation of the DbChange instance before it gets interpreted and turned into SQL statements.

Only for Aggregate Roots events get fired, since these are the abstraction the repositories work on.
Insert and Update events got removed, since this distinction doesn't exist on the Aggregate Root level.
It only exists on the level of entities and/or tables which is represented by DbActions.

Improved some tests to properly check all the events triggered.
@gregturn
Copy link
Contributor

That's merged via 1f2dc16!

@gregturn gregturn closed this Aug 15, 2017
@gregturn gregturn deleted the issue/DATAJDBC-120 branch August 15, 2017 14:27
mp911de added a commit that referenced this pull request Feb 21, 2022
We now provide an annotation-based activation model for R2DBC repositories. Configuration classes can be annotated with @EnableR2dbcRepositories and configuration infrastructure will scan for bean definitions to implement declared R2DBC repositories.

Original pull request: #17.
mp911de pushed a commit that referenced this pull request Feb 21, 2022
Add missing header & package-info. Update nullability and add tests.

Original pull request: #17.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants