Closed Bug 1194824 Opened 9 years ago Closed 9 years ago

Add a "last_modified" column to exclusion profiles table

Categories

(Tree Management :: Treeherder: API, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: KWierso, Assigned: mdoglio)

References

Details

Attachments

(1 file)

46 bytes, text/x-github-pull-request
emorley
: review+
Details | Review
I'd like it if exclusion profiles returned a timestamp of the most recent time they were updated.
This would help me do things like notify all clients when the active exclusion profiles have been update <somewhere else>, prompting them to refresh to pick up the new changes.
Mauro said he'd take a look at this sometime next week, because Mauro is good people. :)
Assignee: nobody → mdoglio
Priority: -- → P3
Mauro, ping? :)
Flags: needinfo?(mdoglio)
Attached file PR 957
Flags: needinfo?(mdoglio)
Attachment #8659861 - Flags: review?(emorley)
To land this on staging/production we need a bit of coordination because there's a db change.
Attachment #8659861 - Flags: review?(emorley) → review+
I applied these db schema changes to both staging and production:
alter table `exclusion_profile` add column `modified` datetime default CURRENT_TIMESTAMP;
alter table `exclusion_profile` modify column `modified` datetime NOT NULL;
I actually set `DEFAULT CURRENT_TIMESTAMP` so that we don't get errors before we land the code:
alter table `exclusion_profile` modify column `modified` datetime default CURRENT_TIMESTAMP;
(In reply to Mauro Doglio [:mdoglio] from comment #7)
> I applied these db schema changes to both staging and production:

Could you also update Heroku's RDS instance please :-)
Flags: needinfo?(mdoglio)
Ooops I forgot about the heroku deployment. Done.
Flags: needinfo?(mdoglio)
Thank you :-)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Depends on: 1304078
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: