Silvan f0ff638db7 fix(handler): report error correctly (#9926) ...

# Which Problems Are Solved

1. The projection handler reported no error if an error happened but
updating the current state was successful. This can lead to skipped
projections during setup as soon as the projection has an error but does
not correctly report if to the caller.

2. Mirror projections skipped as soon as an error occures, this leads to
unprojected projections.

3. Mirror checked position wrongly in some cases

# How the Problems Are Solved

1. the error returned by the `Trigger` method will will only be set to
the error of updating current states if there occured an error.

2. triggering projections checks for the error type returned and retries
if the error had code `23505`

3. Corrected to use the `Equal` method

# Additional Changes

unify logging on mirror projections

2025-05-26 12:55:30 +03:00

..

cockroach

fix(eventstore): use decimal, correct mirror (#9906)

2025-05-20 14:58:32 +03:00

dialect

fix(eventstore): use decimal, correct mirror (#9906)

2025-05-20 14:58:32 +03:00

migrate

feat(cli): init cli (#3186)

2022-02-09 15:01:19 +01:00

mock

chore: use pgx v5 (#7577)

2024-03-27 15:48:22 +02:00

postgres

feat: add task queue (#9321)

2025-02-12 14:51:55 +00:00

database_test.go

perf(query): remove transactions for queries (#8614)

2024-11-04 10:06:14 +01:00

database.go

fix(handler): report error correctly (#9926)

2025-05-26 12:55:30 +03:00

type_test.go

chore: use pgx v5 (#7577)

2024-03-27 15:48:22 +02:00

type.go

chore: use pgx v5 (#7577)

2024-03-27 15:48:22 +02:00