From: Mike Bayer Date: Fri, 15 Jan 2021 15:23:36 +0000 (-0500) Subject: documentation fixes X-Git-Tag: rel_1_5_0~5 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f47f62c7b568243f6068b071fa9e387563ef9499;p=thirdparty%2Fsqlalchemy%2Falembic.git documentation fixes Change-Id: I1f2e8376ce86886a9b35fa48cb7a78ca1735095c --- diff --git a/docs/build/conf.py b/docs/build/conf.py index 45995b3c..75d91edc 100644 --- a/docs/build/conf.py +++ b/docs/build/conf.py @@ -249,6 +249,6 @@ latex_documents = [ autoclass_content = "both" intersphinx_mapping = { - "sqla": ("http://www.sqlalchemy.org/docs/", None), + "sqla": ("https://docs.sqlalchemy.org/en/latest/", None), "python": ("http://docs.python.org/", None), } diff --git a/docs/build/cookbook.rst b/docs/build/cookbook.rst index 4277ad1c..611b4548 100644 --- a/docs/build/cookbook.rst +++ b/docs/build/cookbook.rst @@ -827,6 +827,7 @@ schema or another. __table_args__ = { "schema": None } + .. 2. The :paramref:`.EnvironmentContext.configure.include_schemas` flag must diff --git a/docs/build/unreleased/748.rst b/docs/build/unreleased/748.rst index 9e20003f..b4ee377c 100644 --- a/docs/build/unreleased/748.rst +++ b/docs/build/unreleased/748.rst @@ -1,6 +1,6 @@ .. change:: - :tags: change - :tickets: 711 + :tags: changed + :tickets: 748 Alembic 1.5.0 now supports **Python 2.7 and Python 3.6 and above**, as well as **SQLAlchemy 1.3.0 and above**. Support is removed for Python 3 diff --git a/docs/build/unreleased/autocommit.rst b/docs/build/unreleased/autocommit.rst index 39d60985..61ba5be9 100644 --- a/docs/build/unreleased/autocommit.rst +++ b/docs/build/unreleased/autocommit.rst @@ -1,21 +1,21 @@ .. change:: - :tags: change, environment + :tags: changed, environment - To accommodate SQLAlchemy 1.4 and 2.0, the migration model now no longer - assumes that the SQLAlchemy Connection will autocommit an individual - operation. This essentially means that for databases that use - non-transactional DDL (pysqlite current driver behavior, MySQL), there is - still a BEGIN/COMMIT block that will surround each individual migration. - Databases that support transactional DDL should continue to have the - same flow, either per migration or per-entire run, depending on the - value of the :paramref:`.Environment.configure.transaction_per_migration` - flag. + To accommodate SQLAlchemy 1.4 and 2.0, the migration model now no longer + assumes that the SQLAlchemy Connection will autocommit an individual + operation. This essentially means that for databases that use + non-transactional DDL (pysqlite current driver behavior, MySQL), there is + still a BEGIN/COMMIT block that will surround each individual migration. + Databases that support transactional DDL should continue to have the + same flow, either per migration or per-entire run, depending on the + value of the :paramref:`.Environment.configure.transaction_per_migration` + flag. .. change:: - :tags: change, environment + :tags: changed, environment - It now raises a :class:`.CommandError` if a ``sqlalchemy.engine.Engine`` - is passed to the :meth:`.MigrationContext.configure` method instead of - a ``sqlalchemy.engine.Connection`` object. Previously, this would - be a warning only. \ No newline at end of file + A :class:`.CommandError` is raised if a ``sqlalchemy.engine.Engine`` is + passed to the :meth:`.MigrationContext.configure` method instead of a + ``sqlalchemy.engine.Connection`` object. Previously, this would be a + warning only. \ No newline at end of file