1153 | | In addition, any user that is maintaining an external database backend will need to update their code to use the new interface. The new class-based approach should make backend development much easier, as common behavior can be inherited from the base classes in django.db.backends; only database-specific behavior should require implementation. |
| 1153 | Users that have written custom test runners will also be affected; the `create_test_db()` and `destroy_test_db()` helper methods (plus a few other methods utilized by these two) have been moved into the database backend as part of the creation interface. You can access these methods using `connection.creation.create_test_db()` and `connection.creation.destroy_test_db()` |
| 1154 | |
| 1155 | Lastly, any user that is maintaining an external database backend will need to update their code to use the new interface. The new class-based approach should make backend development much easier, as common behavior can be inherited from the base classes in django.db.backends; only database-specific behavior should require implementation. |