4f9df08373
The 'check_foreign_key' method was removed in oslo.db 1.4.0 [1] and re-added but marked as deprecated in 1.4.1 [2] to allow for a deprecation period. That was over 6 years ago so we can now remove it. Meanwhile, the private '_walk_versions', '_migrate_down' and '_migrate_up' methods have been marked as deprecated since oslo.db 0.5.0 (!!!) [3]. We can definitely remove these now. codesearch.o.o reveals no users of any of these methods. [1] I77a2bba2de08125b5a601de03c1d2d5c73fa33ee [2] Id892567bd60d6b4b88765bbfe3cd5c5e75910b25 [3] Ic9358445e60a0dd43a5900e8bda7b12f2bebf679 Change-Id: Idb9596284df3e5d038c939d27fe14fe2cc2f4318 Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
13 lines
578 B
YAML
13 lines
578 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The ``check_foreign_keys`` helper of the
|
|
``oslo_db.sqlalchemy.test_migrations.ModelsMigrationsSync`` base test class
|
|
has been removed. This was deprecated in 1.4.1 as alembic now supports this
|
|
capability.
|
|
- The ``_walk_versions``, ``_migrate_down``, and ``_migrate_up`` methods of
|
|
the ``oslo_db.sqlalchemy.test_migrations.ModelsMigrationsSync`` base test
|
|
class have been removed. These were deprecated in 0.5.0 in favour of their
|
|
non-private equivalents, ``walk_versions``, ``migrate_down``, and
|
|
``migrate_up`` respectively.
|