audit_logs: entity/migration disagree on http_method type, version, a… - #1214
Merged
RUKAYAT-CODER merged 2 commits intoAug 21, 2026
Conversation
…nd timestamp audit_logs: entity/migration disagree on http_method type, version, and timestamp
Contributor
|
Thank you for contributing to the project. |
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.
Summary
This PR resolves the schema mismatch between the
AuditLogentity and thecreate-audit-log-tablemigration.Changes Made
http_methoddefinition between the entity and database migration.versioncolumn so the entity and migration use the same schema.timestampcolumn to use the same timezone-aware definition across the entity and migration.Problem
The migration defined
http_methodasvarcharand included aversioncolumn, while theAuditLogentity definedhttp_methodas an enum and did not includeversion.Additionally, the migration defined
timestampastimestamptz, while the entity mapping did not explicitly use the timezone-aware type.These differences caused schema synchronization to attempt changes to the existing audit log table.
Result
The
AuditLogentity and database migration are now consistent, preventing schema drift and ensuring the audit log table is created and maintained with the expected column types and definitions.Closes #1203