-
Notifications
You must be signed in to change notification settings - Fork 9
User to aggregatemetric notification #201
Conversation
Applied fixes from StyleCI
CREATE INDEX "tracker_aggregate_metric_spec_branch" ON "tracker_aggregate_metric_spec" ("branch"); | ||
|
||
CREATE TABLE IF NOT EXISTS "tracker_user2aggregate_metric_spec" ( | ||
"id" serial PRIMARY KEY, |
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.
This is counter to our general convention of <table_name>_id
.
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.
Does the MySQL table have a primary key? If not, this is correct.
Other than the nits (which may be illegitimate as @jamiesnape suggests), LGTM. |
It has a primary compound key
Looking at this more carefully, I don't have the corresponding unique compound indices in pgsl and sqlite. Perhaps the way forward is to
Thoughts? |
I guess whatever we normally do in our |
Ahem. I'll follow |
@cpatrick PTAL. This changeset is small since your last checkpoint. |
LGTM. |
…tification User to aggregatemetric notification
@cpatrick PTAL.
The backend to setting up aggregate metric notifications. Some of it anyway.