-
Notifications
You must be signed in to change notification settings - Fork 384
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
Update UserGroupEvent
details format and log interface
#9487
Conversation
f377305
to
2381c4b
Compare
// The format of `details` before this was not finalised, and on | ||
// production nothing important was logged anyway. No going back! | ||
UserGroupEvent::truncate(); |
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.
note that there may still be old events come in after the migration because the migration is run before code deploy
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.
true, should I change anything here to account for that? or just ask peppy to truncate again after deploy?
database/migrations/2022_11_06_022852_require_user_group_events_details_and_type.php
Outdated
Show resolved
Hide resolved
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.
@peppy please run the migration eventually. The exact timing shouldn't matter. It's just dropping existing data and adding null check to the columns which should already be always filled in.
part 2
UserGroupEvent
model #9486