-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Improve notifications to fix commit notification and support release notification #34803
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
base: main
Are you sure you want to change the base?
Conversation
if ctx.IsSigned && !release.IsTag { | ||
err = activities_model.SetReleaseReadBy(ctx, release.ID, ctx.Doer.ID) | ||
if err != nil { | ||
ctx.ServerError("SetReleaseReadBy", err) |
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.
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.
Could you point me to the link for the proposed approach?
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 just reiterated it again recently:
|
||
updatedByIndex := schemas.NewIndex("idx_notification_updated_by", schemas.IndexType) | ||
updatedByIndex.AddColumn("updated_by") | ||
indices = append(indices, updatedByIndex) |
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.
Are these indices well-designed and correct?
You can't just add index to every column and expect that "oh it should work".
Does database work really work that way?
This PR improved notifications.