Morten, Dropping the dry run is OK if, and I stress if, the import process itself becomes more transparent and step-wise. Basically this means 1. Display new records coming in, with the ability to remove all or some from import 2. Display updated records coming in and the equivalent existing records, with the ability to remove all or some from import/updating.
The fundamental problem with DHIS2 imports are that they are "black boxes", you cannot see what's happening until after it's done. Without even the dry run, your only "Safety net" is to back up the whole database just before importing - which is tricky to do in a production environment when manager A imports data while user B,C,D, and E are capturing data directly. Regards Calle On 2 February 2016 at 10:15, Morten Olav Hansen <morte...@gmail.com> wrote: > Hi everyone > > I'm currently in the process of re-writing our DXF2 metadata importer, and > was wondering if anyone is actually using the dryRun option? its adds quite > a bit of complexity to the code, so it will be added only to the new > importer if people are actually using it for imports > > -- > Morten > > _______________________________________________ > Mailing list: https://launchpad.net/~dhis2-devs > Post to : dhis2-devs@lists.launchpad.net > Unsubscribe : https://launchpad.net/~dhis2-devs > More help : https://help.launchpad.net/ListHelp > > -- ******************************************* Calle Hedberg 46D Alma Road, 7700 Rosebank, SOUTH AFRICA Tel/fax (home): +27-21-685-6472 Cell: +27-82-853-5352 Iridium SatPhone: +8816-315-19119 Email: calle.hedb...@gmail.com Skype: calle_hedberg *******************************************
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
