Silvan 59e57af52b fix(mirror): ensure multiple runs (#9899) ...

# Which Problems Are Solved

1. After second execution, mirror starts to fail because of Primary key
constraints on the events table. Because mirror always took the the
first `system.mirror.succeeded` instead of the newest one
2. Mirror panicked during migration of fields tables

# How the Problems Are Solved

1. Adjusted the database query to order descending and limit 1
2. added missing assignment

# Additional Changes

- detailed logging if the copy from statement failed.

2025-05-19 11:30:11 +02:00

..

avatar

refactor(v2): init events (#7823)

2024-05-23 06:36:08 +02:00

database

fix(eventstore): use decimal for position (#9881)

2025-05-14 10:14:08 +00:00

domain

refactor(v2): init events (#7823)

2024-05-23 06:36:08 +02:00

eventstore

fix(eventstore): use decimal for position (#9881)

2025-05-14 10:14:08 +00:00

instance

refactor(v2): init events (#7823)

2024-05-23 06:36:08 +02:00

org

refactor(v2): init events (#7823)

2024-05-23 06:36:08 +02:00

policy

refactor(v2): init events (#7823)

2024-05-23 06:36:08 +02:00

projection

feat(cmd): mirror (#7004)

2024-05-30 09:35:30 +00:00

readmodel

fix(mirror): ensure multiple runs (#9899)

2025-05-19 11:30:11 +02:00

system

fix(eventstore): use decimal for position (#9881)

2025-05-14 10:14:08 +00:00

user

refactor(v2): init events (#7823)

2024-05-23 06:36:08 +02:00