Now that we think we know what we're doing, I'm using a more rigorous approach to defining iterations and tags, and this condition is no longer necessary, and in fact, may be harmful. This I'm removing it. The initial load of data will have these values. iter | tag | purpose --------|-------------|------------------------------------------------- plan | baseline | Adjustments will be made to these values only. actuals | open-orders | Ordered before 2024 season, still open. actuals | booked | Ordered in 2024 season so far |
||
|---|---|---|
| .. | ||
| addmonth_vupd.sql | ||
| adj_totals.sql | ||
| get_pool.sql | ||
| list_changes.sql | ||
| new_basket.sql | ||
| scale_pd.sql | ||
| scale_vd.sql | ||
| scale_vupd_sales.sql | ||
| scale_vupd.sql | ||
| scenario_package.sql | ||
| swap_cust.sql | ||
| swap_fit.sql | ||
| swap_post.sql | ||
| undo.sql | ||