-
Notifications
You must be signed in to change notification settings - Fork 0
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.
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
feat: reorg detector add warnings and store in DB the reorg detection #242
base: develop
Are you sure you want to change the base?
Conversation
|
DROP TABLE IF EXISTS reorg_event; | ||
|
||
-- +migrate Up | ||
CREATE TABLE reorg_event ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need some primary key for the table?
SubscriberID: id, | ||
CurrentHash: currentHeader.Hash(), | ||
TrackedHash: hdr.Hash, | ||
ExtraData: struct { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the usage of ExtraData
field? I don't see its value if it is only used on this place. I would say, just make these two regular fields in the ReorgEvent
.
ExtraData interface{} | ||
} | ||
|
||
type eventReorgRow struct { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the point of meddler is to not have struct conversion before saving it to the db
, because he is the one that does that in the background. So, I would say we don't need this struct.
Description
reorg_event
with reorg detailsFixes #121