Implement Fee Schedule History (table, trigger, and backfill of 2025-01-03 snapshot)
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Introduce Fee Schedule History so that fee schedule changes are auditable:
add a history table and trigger to record changes going forward, and backfill the table with the 2025-01-03 snapshot produced in https://github.com/bcgov/entity/issues/32829.
Scope
- Database (migration)
- [ ] Create Fee Schedule History table (schema and columns as per design).
- [ ] Add trigger(s) on the relevant fee schedule table(s) to insert/update history rows on INSERT/UPDATE/DELETE.
- Backfill
- [ ] After the migration is deployed to the target environment, run a one-time load to insert the data from Ticket 32829 export into the history table, with effective/snapshot date 2025-01-03, as the first historical records.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Review the fee schedule table design and relevant migration entry points, then inspect the Ticket 32829 export; done means the history table and change triggers are deployed and the 2025-01-03 snapshot is loaded as the first historical records.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100