Keeping auditor tables up to date after source tables change
Bug #1768869 reported by
Josh Stompro
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Evergreen |
Fix Released
|
Medium
|
Unassigned |
Bug Description
EG 2.10 upgrading to EG 3.1
I noticed that the new fields for tracking merge info and visibility were missing from our auditor.
Should the upgrade process address keeping existing auditor tables up to date? Or perhaps it just warrants a release note entry that it is something that needs to be dealt with?
Josh
Changed in evergreen: | |
status: | New → Confirmed |
Changed in evergreen: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
There are 10 audited tables in a stock EG install. I think it's reasonable to expect schema updates to those 10 tables to be accompanied by SQL for making the corresponding changes to the auditor tables.
Maybe we want a pgTAP test that compares auditor vs audited?