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
..
avatar	refactor(v2): init events (#7823)	2024-05-23 06:36:08 +02:00
database	fix(eventstore): precise decimal (#8527)	2024-09-06 12:19:19 +03:00
domain	refactor(v2): init events (#7823)	2024-05-23 06:36:08 +02:00
eventstore	fix(eventstore): precise decimal (#8527)	2024-09-06 12:19:19 +03: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(eventstore): precise decimal (#8527)	2024-09-06 12:19:19 +03:00
system	fix(eventstore): precise decimal (#8527)	2024-09-06 12:19:19 +03:00
user	refactor(v2): init events (#7823)	2024-05-23 06:36:08 +02:00