Change default for logs_per_block & max_logs_kept columns from NULL to 0 #12213
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During PR review of #11949, we decided to change the types of [ max_logs_kept / MaxLogsKept ]
and[ logs_per_block / LogsPerBlock ] from [ NUMERIC / *big.Int ] to [ BIGINT / uint64 ]. I intended the default value to be 0 now instead of NULL,
but forgot to add the corresponding NOT NULL DEFAULT 0 clause to these columns in the db schema