update readme, get rid of old file

readme.md

@@ -1,13 +1,13 @@
+pre-requisites
 * setup postgres db with a username and password and database
 * add this to .bashrc to quickly invoke command line connection `export PGD="psql -U ptrowbridge -d ubm -p 5433 -h 192.168.1.110"`
+
 setup
-----------------------------------------------------------------------------------------------------------------------------------------------------
+* `$PG -f setup_sql/schema.sql` setup the application tables 
-* setup the application tables `$PGD -f setup_sql/schema.sql`
 * create a table of data to forecast
-* edit `target_info.sql` to reflect the name of the table from previous step
+* `$PG -f setup_sql/target_info.sql` to populate the meta table (edit table name)
-* `$PGD -f setup_sql/target_info.sql` to populate the meta table
+* fill out the `target_meta` table
-* fill out the `target_meta` table in the database to model the forecast table
+* `$PG -f setup_sql/build_maste_tables.sql` to create master data tables from forecast data
-* `PGD -f setup_sql/build_maste_tables.sql` to create master data tables from forecast data
 * `./routes/baseline/generate_route_sql.sh` to create the baseline sql used by the /baseline route
 
 | schema  | tname   | cname          | opos | func         | fkey         | fcol           | dtype   | appcol       | pretty | 
@@ -44,45 +44,7 @@ setup
     * iter    (added if missing)
     * logid   (added if missing)
 
-routes
+issues
-----------------------------------------------------------------------------------------------------------------------------------------------------
+ - [x] validate the ability to join to associated date tables, for example order season that needs incremented
-* all routes would be tied to an underlying sql that builds the incremental rows
+ - [ ] there is not currently any initial grouping to limit excess data from all the document# scenarios
-* that piece of sql will have to be build based on the particular sales layout
+ - [ ] how to handle a target value adjustment, which currency is it in?
-    * **columns:** a function to build the columns for each route
-    * **where** a function to build the where clause will be required for each route
-    * the result of above will get piped into a master function that build the final sql
-    * the master function will need to be called to build the sql statements into files of the project
-
-
-route baseline
-----------------------------------------------------------------------------------------------------------------------------------------------------
-* forecast = baseline (copied verbatim from actuals and increment the dates) + diffs. if orders are canceled this will show up as differ to baseline
-* regular updates to baseline may be required to keep up with canceled/altered orders
-* copy some period of actual sales and increment all the dates to serve as a baseline forecast
-
-- [x] join to period tables to populate season; requires variance number oof table joins, based on howmany date functions there are 🙄
-- [ ] some of the app parameters can be consolidated, the baseline period could be one large range potentially, instead of 2 stacked periods
-- [x] setup something to fill in sql parameters to do testing on the function
-- [ ] update node to handle forecast name parameter
-- [ ] calc status is hard-coded right now in the json request -> probably needs to be manuall supplied up front
-
-scale
-----------------------------------------------------------------------------------------------------------------------------------------------------
-- [x] need to add version columns to all CTE's
-- [ ] need to build log insert
-- [x] Need to build where clause for scenario
-
-running problem list
-----------------------------------------------------------------------------------------------------------------------------------------------------
-* baseline route
-    - [x] problem: how will the incremented order season get updated, adding an interval won't work
-        * a table fc.odate, has been built, but it is incomplete, a setup function filling in these date-keyed tables could be setup
-        * if a table is date-keyed, fc.perd could be targeted to fill in the gaps by mapping the associated column names
-    - [x] problem: the target sales data has to map have concepts like order_date, and the application needs to know which col is order date
-        * add column called application hook
-    - [ ] there is not currently any initial grouping to limit excess data from all the document# scenarios
-* general
-    - [ ] clean up SQL generation to prevent injection
-    - [ ] how to handle a target value adjustment, which currency is it in?
-    - [ ] **the sales data has to have a column for module and change ID, live sales data isn't going to work well**
-        - [ ] need to target the live sales data, build build a whole new table to use it plus add version columns

routes/edit_meta/readmeta.sql

@@ -1,13 +0,0 @@
-SELECT
-    tname
-    ,cname
-    ,opos
-    ,func
-    ,fkey
-    ,pretty
-    ,dtype
-    ,mastcol
-    ,appcol
-    ,dateref
-FROM
-    fc.target_meta