fix(schedules): updated_at automatically updates to any change to row

[ecrupper]

Existing schedule:

  {
    "id": 1,
    "repo_id": 1,
    "active": true,
    "name": "hourly",
    "entry": "0 * * * *",
    "created_at": 1641314085,
    "created_by": "octokitty",
    "updated_at": 1641314085,
    "updated_by": "octokitty",
    "scheduled_at": 0
  }

Old:

s := existingSchedule
s.SetScheduledAt(now)
_ := db.UpdateSchedule(s)

s, _ := db.GetSchedule(existingSchedule)
fmt.Println(s.GetUpdatedAt())
// ... <now> ...

New:

s := existingSchedule
s.SetScheduledAt(now)
_ := db.UpdateSchedule(s)

s, _ := db.GetSchedule(existingSchedule)
fmt.Println(s.GetUpdatedAt())
// ... 1641314085 ...

GORM auto updates updated_at. This change ensures that that field is still relevant.

RFC: separate DB function altogether, or will this boolean be fine?

[codecov]

Codecov Report

Merging #894 (2f3a677) into main (45c6007) will increase coverage by 0.00%.
The diff coverage is 77.77%.

@@           Coverage Diff           @@
##             main     #894   +/-   ##
=======================================
  Coverage   71.47%   71.48%           
=======================================
  Files         304      304           
  Lines       12436    12438    +2     
=======================================
+ Hits         8889     8891    +2     
  Misses       3116     3116           
  Partials      431      431           

Impacted Files	Coverage Δ
api/schedule/create.go	8.87% <0.00%> (ø)
api/schedule/update.go	0.00% <0.00%> (ø)
database/schedule/update.go	84.21% <100.00%> (+1.85%)	⬆️

[jbrockopp]

LGTM - I'm good the boolean approach

[jbrockopp]

LGTM

[wass3rw3rk]

lgtm

[wass3rw3rk]

lgtm