db upgrade failures should be handled better
Bug #496373 reported by
Michael Rooney
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| wxBanker |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
If a database upgrade fails, right now it can be confusing on how to continue using wxBanker, especially because if not running from a terminal the error is completely silent!
So it should:
* Automatically roll back from the backup (so that the upgrade attempt is idempotent)
* Use wxPython to display an error dialog
* Explain that the upgrade failed, the old database has been restored, and to use the old version of wxBanker
* Provide a link to file a bug and highly encourage the user to do so
Related branches
lp:~danielalmaguer/wxbanker/Db_Fallback
- wxBanker Developers: Pending requested
-
Diff: 76 lines (+43/-2)1 file modifiedwxbanker/persistentstore.py (+43/-2)
| Changed in wxbanker: | |
| assignee: | nobody → Michael Rooney (mrooney) |
| importance: | Undecided → Medium |
| milestone: | none → 0.6.1 |
| status: | New → In Progress |
Revision history for this message
| Michael Rooney (mrooney) wrote | #1 |
| Changed in wxbanker: | |
| assignee: | Michael Rooney (mrooney) → nobody |
| milestone: | 0.6.1 → future |
| status: | In Progress → Triaged |
To post a comment you must log in.
It is more important to get out the release for now, this can be handled later. Hopefully with the testing infrastructure now in place it won't happen!