Add new checker for tables without default timestamp columns#197
Merged
gregnavis merged 1 commit intogregnavis:masterfrom Jan 3, 2025
Merged
Add new checker for tables without default timestamp columns#197gregnavis merged 1 commit intogregnavis:masterfrom
gregnavis merged 1 commit intogregnavis:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Just found a few tables in our app not having
created_at/updated_atcolumns. This was done accidentally. Now, without these columns it is hard to tell if the table is used or not.In 99.9% of cases, tables should have these columns. Without them, it is also impossible to know when the record was created/updated (which can greatly help debugging). Also the use of Rails automatic cache expiration based on updated_at column is impossible.