Meeting with Eric about the sales tax aggregates
4/19/21
- order of events
- branch name - elt-salesTaxAggregation

1. create the objects - new tables and new columns
2. setup the triggers
3. setup the schedules
4. run the primary update

////////////
- do data 0 first (step by step)
- make sure that things exist, but no dependencies (at first)
- there is a timing issue
- known files - invoice DAO (cfc) and search 10 (cfc)
- when the first rollout happens, collaspe the existing table rows in the aggregate table.
- kinda let it build potentially incorrect entries (don't worry about it right away - it will catch itself up)
- it may be fun to see what the data looks like before destroying it.
- locally (localhost) - there shouldn't be a problem - no timing issues
- live or production - there is a possible timing issue
- the truncate only needs to be the very first time. after that, we do not want it.
- we talked about using different branches r1, r2, etc. - leaning towards that - r1 and r2 could be selfcontained in the same db update with different links
- we may be able to add a dummy row... once that gets removed, we don't care and move forward
- at night, we add new rows - during the day, the triggers keep anything older up to date
- what about invoices that shouldn't be included in the sales tax aggregates