1dd87ad197
Format all source code using Prettier
8 years ago
2e4893f4c1
Clarify implications of introducing new migrations
8 years ago
7413b787b6
Make `migrations` private
8 years ago
805031ade8
Conditionally run post-attachment migrations
...
Introduce placeholder migrations for Backbone models so they never implicitly
run migrations whenever they are `fetch`ed. We prefer to run our migrations
explicitly upon app startup and then let Backbone models be (slightly) dumb(er)
models, without inadvertently triggering migrations.
8 years ago
bfbeedab5c
Temporarily disable post-attachment migration migrations
8 years ago
4ff8bc3357
Use `camelCase` for non-constructors
8 years ago
172616ca4f
Add log message for dummy migration 18
8 years ago
da144edc56
Manually close database connection after migration
8 years ago
fcd30cd919
Close database after migration
...
This is not 100% reliable as database connections are closed in a separate
thread according to the documentation:
- https://developer.mozilla.org/en-US/docs/Web/API/IDBDatabase/close
- https://stackoverflow.com/a/18639298
- 80c7a06d5c/backbone-indexeddb.js (L558-L565)
8 years ago
e2f1339ab9
Explicitly run post-attachment migrations
8 years ago
d16178638e
Split database migrations into pre- and post-attachment migration
...
- Run light-weight migrations before attachment migration.
- Run regular migrations after attachments have been moved to disk.
8 years ago
Daniel Gasienica