It seems there is some confusion what reload really means. pje's understanding was that it be used only as an upgrade path/data migration path, meaning the expectation on reload is for all userdata to go away and be replaced with what is in the dump.
However, my understanding of some of the reload code seems to be that it is acting more like an import, i.e. adding that data in the dump to the current repository. The current reload menu item perpetrates this import interpretation of this as well; if it was truly about reload then it should restart chandler with --create and use some new option to point to the dump. Can we agree that reload means "blow away all current data and reload dump"? If so, we have some work to do... -- Heikki Toivonen
signature.asc
Description: OpenPGP digital signature
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Open Source Applications Foundation "chandler-dev" mailing list http://lists.osafoundation.org/mailman/listinfo/chandler-dev
