pt/pivot_forecast
1
0
Fork 0
Code Issues 1 Pull Requests Projects Releases Wiki Activity

notes on issues

Browse Source
This commit is contained in:
Paul Trowbridge 2022-04-13 01:15:07 -04:00
parent 298e2fdc4e
commit d77b7910d5
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
readme.md
View File

@ -30,11 +30,11 @@ setup
* a foreign key and table is setup (except date types)
* baseline function does a group-by to compact data for any func/appcol and value types are aggregated
* fkey:
* primary key of assoicated data and join basis
* primary key of assoicated data and foreign key basis
* for date types no foreign key is setup, but dynamic table joins use the fkey field to join on
* fcol: associated field from the master data table if it is different (oseas would refer to ssyr in fc.perd)
* pretty: display column name (user friendly)
* appcol: parameters that will have to be supplied but the application
* appcol: flag columns that will be needed by the application
* order_date
* ship_date
* customer
@ -48,7 +48,10 @@ setup
* logid (added if missing)
issues
- [ ] what if you create a func table but some of the values are null? (orders without quotes)
- [x] what if you want certain things like invoice numbers included in the baseline, is a func table necesary? no, just leave fkey null and no table will be setup
- [ ] baseline needs to populate all columns in sequential order like the scale route
- [ ] what if there is more than one table in fc.target_meta
- [x] validate the ability to join to associated date tables, for example order season that needs incremented
- [ ] there is not currently any initial grouping to limit excess data from all the document# scenarios
- [ ] how to handle a target value adjustment, which currency is it in?