New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[v4] ESDB history: split in events and debug table #11

Open

wmertens opened this issue Dec 14, 2020 · 0 comments

Collaborator

wmertens commented Dec 14, 2020

Since

event processing happens in a single transaction
the event itself is used as a scratch space for dispatching subevents
stored results are not used currently by ESDB
stored results will likely not be used in the future (secondary copies can repeat the redux cycle, it's pure, and comparing results might spot errors)

...we should move the event result information to a second table.

This:

makes more sense conceptually
improves data fragmentation
allows easily deleting debug data that's no longer interesting
allows emitting one row per subevent for easier debugging

This is a breaking change so belongs in v4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment