zitadel/internal/v2/eventstore
Silvan b522588d98
fix(eventstore): precise decimal (#8527)
# Which Problems Are Solved

Float64 which was used for the event.Position field is [not precise in
go and gets rounded](https://github.com/golang/go/issues/47300). This
can lead to unprecies position tracking of events and therefore
projections especially on cockcoachdb as the position used there is a
big number.

example of a unprecies position:
exact: 1725257931223002628
float64: 1725257931223002624.000000

# How the Problems Are Solved

The float64 was replaced by
[github.com/jackc/pgx-shopspring-decimal](https://github.com/jackc/pgx-shopspring-decimal).

# Additional Changes

Correct behaviour of makefile for load tests.
Rename `latestSequence`-queries to `latestPosition`
2024-09-06 12:19:19 +03:00
..
postgres fix(eventstore): precise decimal (#8527) 2024-09-06 12:19:19 +03:00
aggregate.go refactor(v2): init eventstore package (#7806) 2024-04-26 15:05:21 +00:00
current_sequence.go refactor(v2): init eventstore package (#7806) 2024-04-26 15:05:21 +00:00
event_store.go fix(eventstore): precise decimal (#8527) 2024-09-06 12:19:19 +03:00
event.go refactor(v2): init events (#7823) 2024-05-23 06:36:08 +02:00
push.go feat(cmd): mirror (#7004) 2024-05-30 09:35:30 +00:00
query_test.go fix(eventstore): precise decimal (#8527) 2024-09-06 12:19:19 +03:00
query.go fix(eventstore): precise decimal (#8527) 2024-09-06 12:19:19 +03:00
unique_constraint.go refactor(v2): init eventstore package (#7806) 2024-04-26 15:05:21 +00:00