| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
sqlite doesn't like complex changes (alter table) to happen
inside a transaction that has already done other things.
And really, each migration should say "I'm done" and commit
its changes.
This is not the full story, but it's the core of it.
Specifially the migration framework should probably do a
rollback "just in case" after each migration.
|
| | |
|
| | |
|
| |
|
|
| |
Renamed `ogg' to `webm_audio' in core__file_keynames
|
| |
|
|
|
|
| |
- Various fixes to dbupdate itself
- Switching db/sql/migrations.py to use a dict instead of a list
- Registering the function
|
|
|
Things definitely don't work yet, but should be heading in the right direction.
|
