Ensure pre-processing results in CSVs with correct columns for PostgreSQL import
Closed this issue · 0 comments
edwardchalstrey1 commented
Future versions of the source files may have additional, or differently ordered columns (this is the case for FiT already). We should account for this by checking if the columns exist, putting them in the correct order (as per SQL scripts) and leaving values blank if those columns do not exist in the source files