From 9ec084aa042e0007b1abc88f8c0106bac184ddd4 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Mon, 18 Jan 2021 15:27:01 -0500 Subject: remove all .. version(?:changed|added):: prior to 1.0 Change-Id: I2a1a0c273adc871b12e13d7f913609fe1122dab3 --- docs/build/batch.rst | 23 ----------------------- 1 file changed, 23 deletions(-) (limited to 'docs/build/batch.rst') diff --git a/docs/build/batch.rst b/docs/build/batch.rst index 7cb7a99..e9582c6 100644 --- a/docs/build/batch.rst +++ b/docs/build/batch.rst @@ -3,12 +3,6 @@ Running "Batch" Migrations for SQLite and Other Databases ========================================================= -.. note:: "Batch mode" for SQLite and other databases is a new and intricate - feature within the 0.7.0 series of Alembic, and should be - considered as "beta" for the next several releases. - -.. versionadded:: 0.7.0 - The SQLite database presents a challenge to migration tools in that it has almost no support for the ALTER statement upon which relational schema migrations rely upon. The rationale for this stems from @@ -106,10 +100,6 @@ The reflection process may also be bypassed entirely by sending a pre-fabricated :class:`~sqlalchemy.schema.Table` object; see :ref:`batch_offline_mode` for an example. -.. versionadded:: 0.7.1 - added :paramref:`.Operations.batch_alter_table.reflect_args` - and :paramref:`.Operations.batch_alter_table.reflect_kwargs` options. - .. _sqlite_batch_constraints: Dealing with Constraints @@ -168,10 +158,6 @@ as described in :ref:`autogen_naming_conventions`. Usage is as follows:: Note that the naming convention feature requires at least **SQLAlchemy 0.9.4** for support. -.. versionadded:: 0.7.1 - added :paramref:`~.Operations.batch_alter_table.naming_convention` to - :meth:`.Operations.batch_alter_table`. - Including unnamed UNIQUE constraints ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ @@ -249,11 +235,6 @@ again references the correct table. This operation only works when referential integrity is disabled, consistent with the same requirement for referring foreign keys from other tables. -.. versionchanged:: 0.8.4 Self-referring foreign keys are created with the - target table name in batch mode, even though this table will temporarily - not exist when dropped. This requires that the target database is not - enforcing referential integrity. - When SQLite's ``PRAGMA FOREIGN KEYS`` mode is turned on, it does provide the service that foreign key constraints, including self-referential, will automatically be modified to point to their table across table renames, @@ -296,10 +277,6 @@ preferred style of working; however, if one needs to do SQLite-compatible "move and copy" migrations and need them to generate flat SQL files in "offline" mode, there's not much alternative. -.. versionadded:: 0.7.6 Fully implemented the - :paramref:`~.Operations.batch_alter_table.copy_from` - parameter. - Batch mode with Autogenerate ---------------------------- -- cgit v1.2.1