> Why aren't we using a diff-based import-export?? Suppose I already have an > exported file and the new export file only should contain the new values, we > can generate only the changed values in the export process. Definitely > reduces time/ file size for places where import-export will be used > monthly/weekly. >
We could definitely do this by using the timeStamp property on DataValue and let the user specify a "since" date in the export GUI. But the user is already specifying which months to export data for, typically only the last month so I am not sure how much we would save on the file size... > Has anyone thought of object serialization?? Where we could serialize > objects and move it to new places... A radical and stupid way, but may be > useful for GIS import-export, where the dxf format may fall short on > representing sharable geographic information. Disease surveillance on the > CBHS may be one candidate... >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
