From 13f9578082ae669734d65a38cb6058e21df88362 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Sat, 18 Jun 2016 09:35:54 -0400 Subject: [PATCH] - update alembic link Change-Id: I5ac6ba8234873fdd19bee6c1decd311a9cb4d55e --- doc/build/conf.py | 2 +- doc/build/core/constraints.rst | 2 +- doc/build/core/metadata.rst | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/build/conf.py b/doc/build/conf.py index 8f01adf866..ec9313678f 100644 --- a/doc/build/conf.py +++ b/doc/build/conf.py @@ -373,7 +373,7 @@ epub_copyright = u'2007-2015, SQLAlchemy authors' #epub_tocdup = True intersphinx_mapping = { - 'alembic': ('https://alembic.readthedocs.io/en/latest/', None), + 'alembic': ('http://alembic.zzzcomputing.com/en/latest/', None), 'psycopg2': ('http://pythonhosted.org/psycopg2', None), } diff --git a/doc/build/core/constraints.rst b/doc/build/core/constraints.rst index bede2b00f0..bf47a5b611 100644 --- a/doc/build/core/constraints.rst +++ b/doc/build/core/constraints.rst @@ -426,7 +426,7 @@ parameters which create :class:`.UniqueConstraint` and :class:`.Index` objects without an explicit name being specified. The use case of alteration of existing tables and constraints can be handled -by schema migration tools such as `Alembic `_. +by schema migration tools such as `Alembic `_. However, neither Alembic nor SQLAlchemy currently create names for constraint objects where the name is otherwise unspecified, leading to the case where being able to alter existing constraints means that one must reverse-engineer diff --git a/doc/build/core/metadata.rst b/doc/build/core/metadata.rst index 8aece0b90f..1e762b188e 100644 --- a/doc/build/core/metadata.rst +++ b/doc/build/core/metadata.rst @@ -243,7 +243,7 @@ database schemas in relation to application code using schema migration tools. There are two major migration tools available for SQLAlchemy: -* `Alembic `_ - Written by the author of SQLAlchemy, +* `Alembic `_ - Written by the author of SQLAlchemy, Alembic features a highly customizable environment and a minimalistic usage pattern, supporting such features as transactional DDL, automatic generation of "candidate" migrations, an "offline" mode which generates SQL scripts, and support for branch -- 2.47.2