[Chandler-dev] Reload is not import
heikki at osafoundation.org
Fri Apr 13 11:52:37 PDT 2007
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
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...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 254 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20070413/f88dce09/signature.pgp
More information about the chandler-dev