Kevin Ansfield f038fbe0aa Fixed "Unable to update nested relation" errors when rolling back migrations ... no issue - we recently started wrapping rollbacks in transactions (https://github.com/TryGhost/knex-migrator/pull/161) - in a number of migrations we were calling `model.destroy()` without passing through the options which includes the current transaction - for models which are using `bookshelf-relations` this could result in an internal `SQLITE_BUSY: database is locked` error because it tries to run queries against tables that have been locked by previous queries in the transaction - by passing through the options when calling `.destroy()` it allows the `bookshelf-relations` to re-use the same transction avoiding the database lock problems		2019-08-20 11:20:52 +01:00
..
1-add-sessions-table.js	Created session table migration (#9908)	2018-09-27 09:51:46 +02:00
2-add-integrations-and-api-key-tables.js	Set up schema and models for API Key authentication (#9904)	2018-10-02 17:46:38 +01:00
3-insert-admin-integration-role.js	Fixed "Unable to update nested relation" errors when rolling back migrations	2019-08-20 11:20:52 +01:00
4-insert-integration-and-api-key-permissions.js	Set up schema and models for API Key authentication (#9904)	2018-10-02 17:46:38 +01:00
5-add-mobiledoc-revisions-table.js	Added mobiledoc_revisions schema, migration script and updated tests	2018-10-02 19:15:23 +02:00