You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Out of the box Sequent uses the Sequent::Core::Persistors::ActiveRecordPersistor for replaying events on a Sequent
migration. When a record has a belongs_to it expects the "parent" record to exist. During replay this is not guaranteed since
the default replay strategy replays on aggregate_id.
Although we don't expect any validations on projections (records) they should probably be skipped explicitly nonetheless, my guess is that would skip the belongs_to check as well.
As work around, and recommendation, you should configure Sequent to use the Sequent::Core::Persistors::ReplayOptimizedPostgresPersistor during replay.
The text was updated successfully, but these errors were encountered:
Out of the box Sequent uses the
Sequent::Core::Persistors::ActiveRecordPersistor
for replaying events on a Sequentmigration. When a record has a
belongs_to
it expects the "parent" record to exist. During replay this is not guaranteed sincethe default replay strategy replays on
aggregate_id
.Although we don't expect any validations on projections (records) they should probably be skipped explicitly nonetheless, my guess is that would skip the
belongs_to
check as well.As work around, and recommendation, you should configure Sequent to use the
Sequent::Core::Persistors::ReplayOptimizedPostgresPersistor
during replay.The text was updated successfully, but these errors were encountered: