pt/tps
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
14 Commits 6 Branches 0 Tags 2 MiB
PLpgSQL 67.8%
JavaScript 12.9%
CSV 10.4%
HTML 8.7%
Shell 0.2%
76dca0d688
Go to file
Paul Trowbridge 76dca0d688 explore options on format
2017-09-19 07:17:38 -04:00
build_json.xlsx explore options on format 2017-09-19 07:17:38 -04:00
coa.md Update coa.md 2017-09-18 17:23:29 -04:00
event_log.md explore options on format 2017-09-19 07:17:38 -04:00
event_log.pgsql link in header 2017-08-24 23:46:15 -04:00
LICENSE add event record example 2017-07-24 23:13:34 -04:00
log.md add excel file with json build macro 2017-09-18 21:07:22 -04:00
new_format.pgsql explore options on format 2017-09-19 07:17:38 -04:00
readme.md add event record example 2017-07-24 23:13:34 -04:00
rec.json updates 2017-08-24 22:57:21 -04:00
ubm.backup add ubm backup 2017-09-18 21:47:37 -04:00

readme.md

Concepts

pull various static files into postgres and do basic transformation without losing the original document or getting into custom code for each scenario

Storage

all records are jsonb applied mappings are in associated jsonb documents

Import

COPY function utilized

Mappings

  1. regular expressions are used to extract pieces of the json objects
  2. the results of the regular expressions are bumped up against a list of basic mappings and written to an associated jsonb document

Transformation tools

  • COPY
  • regexp_matches()

Difficulties

Non standard file formats will require additional logic example: PNC loan balance and collateral CSV files

  1. External: Anything not in CSV should be converted external to Postgres and then imported as CSV
  2. Direct: Outside logic can be setup to push new records to tps.trans direct from non-csv fornmated sources or fdw sources

Interface

maybe start out in excel until it gets firmed up

  • list existing mappings
    • apply mappings to see what results come back
  • experiment with new mappings