add some notes about the dating conundrum
This commit is contained in:
parent
7e3354824c
commit
f382d256ed
@ -29,6 +29,7 @@ route baseline
|
||||
* copy some period of actual sales and increment all the dates to serve as a baseline forecast
|
||||
|
||||
TO-DO:
|
||||
- [ ] join to period tables to populate season; requires variance number oof table joins, based on howmany date functions there are 🙄
|
||||
- [ ] setup something to fill in sql parameters to do testing on the function
|
||||
|
||||
running problem list
|
||||
|
@ -11,6 +11,7 @@ CREATE TABLE fc.target_meta (
|
||||
,dtype text
|
||||
,mastcol text
|
||||
,appcol text
|
||||
,dateref text
|
||||
);
|
||||
|
||||
--ALTER TABLE fc.target_meta DROP CONSTRAINT IF EXISTS target_meta_pk;
|
||||
@ -26,3 +27,4 @@ COMMENT ON COLUMN fc.target_meta.pretty IS 'the presentation name of the column'
|
||||
COMMENT ON COLUMN fc.target_meta.dtype IS 'data type of the sales table column';
|
||||
COMMENT ON COLUMN fc.target_meta.mastcol IS 'associated field from the master data table if it is different (oseas would refer to ssyr in fc.perd)';
|
||||
COMMENT ON COLUMN fc.target_meta.appcol IS 'supply column name to be used for application variables - (specifcy the order date column)';
|
||||
COMMENT ON COLUMN fc.target_meta.dateref IS 'reference to the relevant hard coded perd table column for dates';
|
||||
|
Loading…
Reference in New Issue
Block a user