-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow database relinking attempt during import #428
Conversation
* Fixes product name for newly created activities * Ensure db metadata is updated when change occurs
This will update metadata to ensure 'depends' is correct
This also contains a few bug-fixes for annoyances. |
This is turning out to be really annoying. The database import takes place within a thread, so handling exceptions is exceedingly difficult without halting the thread and restarting it later. A possible solution would be to start a hidden 'fixit' thread and make use of the QWaitCondition if any errors take place. (edit) Though having said it, maybe halting the thread, asking for input and restarting it would be a good fix... |
Due to no standard naming scheme for , it is possible for the local BW2Package import to 'fail' because the dependent databases 'do not exist'.
This pull-request allows users to select, for each database that doesn't exist, an alternative. An attempt is then made to relink all of the relevant exchanges in the import using this other database name instead.
If this still results in an error (the new key doesn't exist), then database import will fail as usual.