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

notes on column purpose

Browse Source
This commit is contained in:
Paul Trowbridge 2022-04-12 23:54:03 -04:00
parent 80bcb23170
commit 298e2fdc4e
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
readme.md
View File

@ -26,8 +26,12 @@ setup
| | | | | | | | | iter | |
| | | | | | | | | logid | |
* func: table name of associated data
* fkey: primary key of assoicated dat
* func:
* 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
* 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
@ -44,6 +48,7 @@ setup
* logid (added if missing)
issues
- [ ] baseline needs to populate all columns in sequential order like the scale route
- [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?