- naming convention limited to SQLA 0.9.4 or greater

diff --git a/alembic/operations.py b/alembic/operations.py
index 6a10f382197eb807330506fee591deae76924ecd..683d2bda3030cd7d41afbd9a44977501dd2a8d57 100644 (file)
--- a/alembic/operations.py
+++ b/alembic/operations.py
@@ -296,7 +296,7 @@ class Operations(object):
          to the :class:`~sqlalchemy.schema.MetaData` during the reflection
          process.  This is typically required if one wants to drop SQLite
          constraints, as these constraints will not have names when
-         reflected on this backend.
+         reflected on this backend.  Requires SQLAlchemy **0.9.4** or greater.
 
          .. seealso::
 

diff --git a/docs/build/batch.rst b/docs/build/batch.rst
index 04a32c4bf28e08fd2e20dde1256050cc93d151eb..307d2a1877a90cdeb63a763e2dff9359320f638e 100644 (file)
--- a/docs/build/batch.rst
+++ b/docs/build/batch.rst
@@ -163,6 +163,9 @@ as described in :ref:`autogen_naming_conventions`.   Usage is as follows::
         batch_op.drop_constraint(
             "fk_bar_foo_id_foo", type_="foreignkey")
 
+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`.

diff --git a/tests/test_batch.py b/tests/test_batch.py
index b71e003f0ca6a28e480ac83188480ec944baa700..70dad5635947193a6bb73b46c7ddcd2b95698f21 100644 (file)
--- a/tests/test_batch.py
+++ b/tests/test_batch.py
@@ -675,6 +675,7 @@ class BatchRoundTripTest(TestBase):
             {"id": 5, "x": 9}
         ])
 
+    @config.requirements.sqlalchemy_094
     @config.requirements.unnamed_constraints
     def test_drop_foreign_key(self):
         bar = Table(