| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Tested on regular PC running Sugar 0.92 on Debian Squeeze with version support
enabled data store.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tested on:
- regular PC running Sugar 0.89 on Debian Squeeze with version support enabled
data store
- restoring a bundle created on the same host into an empty Journal
- restoring a bundle created on the same host again (all entries skipped:
both unmodified and recently modified ones)
- restoring a bundle created from 0.82 data store
- restoring a bundle created from 0.82 data store again (all entries skipped:
both unmodified and recently modified ones)
- restoring a bundle created from 0.84 data store
- restoring a bundle created from 0.84 data store
again (all entries skipped: both unmodified and recently modified ones)
- restoring a bundle containing entries from a version support enabled data
store re-exported from a 0.82 data store (all existing entries skipped:
both unmodified and recently modified ones)
- restoring a bundle containing entries from a version support enabled data
store re-exported from a 0.84 data store (all existing entries skipped:
both unmodified and recently modified ones)
- XO-1.5 running Sugar 0.84.16 on OLPC build 852
- restoring a bundle created on the same host into an empty Journal
- restoring a bundle created on the same host again (all entries skipped:
both unmodified and recently modified ones)
- restoring a bundle created from 0.82 data store
- restoring a bundle created from 0.82 data store again (all entries skipped:
both unmodified and recently modified ones)
- restoring a bundle created from a version support enabled data store
- restoring a bundle created from a version support enabled data store again
(all entries skipped: both unmodified and recently modified ones)
- XO-1 running Sugar 0.82.1 on OLPC build 801
- restoring a bundle created on the same host into an empty Journal
- restoring a bundle created on the same host again (all entries skipped:
both unmodified and recently modified ones)
- restoring a bundle created from a version support enabled data store
- restoring a bundle created from a version support enabled data store again
(all entries skipped: both unmodified and recently modified ones)
All bundles were created using Backup-4.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When restoring multiple versions of the same entry to a data store with version
support, we need to save parents before children (so the base version needs to
come first). Backup will now write them in the right order, assuming the
timestamp was correct. This should be good enough in practice; if we ever
encountered bundles that are not in the right order (e.g. because the timestamp
was messed with), we will need to implement topological sorting (based on
tree_id, parent_id and version_id).
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tested on:
- regular PC running Sugar 0.89 on Debian Squeeze with version support enabled
data store
- restoring a bundle created on the same host into an empty Journal
- restoring a bundle created on the same host again (all entries skipped:
both unmodified and recently modified ones)
- restoring a bundle created from a non-version support enabled data store
- restoring a bundle created from a non-version support enabled data store
again (all entries skipped: both unmodified and recently modified ones)
- restoring a bundle containing entries from a version support enabled data
store re-exported from a non-version support enabled data store (all
existing entries skipped: both unmodified and recently modified ones)
- XO-1.5 running Sugar 0.84.16 on OLPC build 204
- restoring a bundle created on the same host into an empty Journal
- restoring a bundle created on the same host again (all entries skipped:
both unmodified and recently modified ones)
- restoring a bundle created from a version support enabled data store
- restoring a bundle created from a version support enabled data store again
(all entries skipped: both unmodified and recently modified ones)
The data store with version support was the very latest version from git, with
support for specifying a version_id on save() (commit e0d231f).
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We can add UI to handle restore failures (e.g. list of failed entries or a
DOS-style abort/retry/ignore question) later. For now it's more important to
get any feedback at all on restore failures.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit f1eb9444dd3e8f4beb338b8d0cc88aa750630095.
Will split this up into two commits so the git rename-detection
logic hopefully works better.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|