Releases: dimagi/commcare-export
1.3.2
1.3.1
1.3.0
This release includes two significant changes:
- The
--with-organizationflag which provides a simple way to export location data and join it with forms and cases. - Support for a "Data Type" column in excel query files, which allows you to explicitly set the SQL data type of a column. Columns with explicit data types set will also be created immediately, instead of the first time there is data for that property.
1.2.4
Change the Oracle text column from CLOB to VARCHAR2
1.2.3
1.2.2
1.2.1
1.2.0
Upgrade notes
If you are exporting to SQL and using config files with multiple tables (Excel sheets) it is recommended that you do a full re-export of your data to ensure that there is no missing data. You could do this in one of the following ways:
- Use the
--start-overflag to ignore any existing checkpoints. - Edit the file to change the checkpoint key.
- Change the checkpoint key manually using the
commcare-export-utils set-checkpoint-keycommand.
New features
(#123) add sha1 function to allow creating hashes of output values. Mostly useful when exporting nested objects and the jsonpath ID becomes too long for the SQL primary key column.
Improvements / fixes
(#118) Don't set checkpoint to current time. Always use time from batch if available, otherwise don't log a checkpoint.
(#121) Use a separate checkpoint for each table being exported. This impacts any export configurations that have multiple tables configured in one file. Fixes #119
Other Changes
- improvements to console logging
- fix deprecation warnings
