Morgen Sagen wrote:
Back to Heikki's earlier question:
On Apr 13, 2007, at 11:52 AM, Heikki Toivonen wrote:
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.
I was just thinking about this, and it could be quite useful to be
able to dump a given collection to a file and have another Chandler be
able to reload it (without blowing away their repo).
I had a thought that maybe Import should allow you chose a .dump file
and when .dump's are used this way it does act like import. Then again
maybe we are getting too far ahead of ourselves and we just leave this
to be handled in the future, when we have more end user feedback about
what is wanted.
So perhaps the "reload" menu item could ask if you want to replace
your data with what is in the dump file, or add the data to your repo.
Also, I think we need a command line argument that will reload a dump
file, as in:
RunChandler --create --reload /path/to/file.dump
...and that would be used for the upgrade/migration route.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
