fix: insert instead of update new state with updated revision during migration

sebastian-alfers commented 3 months ago

Before this pr, a new migrated state with an evolved revision was attempted to be UPDATEed which failed as there exists no state to be upgraded.

This pr

Applies an INSERT if a state is migrated that does not have an existing revision of its persistence id.
Applies an UPDATE if a state is migrated that does have an existing revision of its persistence id.

sebastian-alfers commented 3 months ago

If we want to drop the primary key setup, lets close this pr, fix #558, and then do this with a proper upsert?

johanandren commented 3 months ago

I agree, that sounds better to me @sebastian-alfers (if we have time to spend on it that is)

sebastian-alfers commented 3 months ago

Closing this to rework for real upsert since https://github.com/akka/akka-persistence-r2dbc/pull/559 is about to get merged.

akka / akka-persistence-r2dbc