Refactor author_name from AuditEvent details
Problem to solve
In an AuditEvent
, the name of the user that triggered the event author_name
is stored within a JSON hash. This is difficult and slow to query and has resulted in data inconsistency within the audit_events
table.
Proposal
See parent proposal: #220116 (closed)
- Migration to introduce new
author_name
column - Route data writes to new columns. Continue populating to
details
(for a milestone) to ensure data correctness - Update data retrieval code to read from newly created columns
Links / references
Edited by Max Woolf