summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/build/conf.py2
-rw-r--r--doc/build/core/constraints.rst2
-rw-r--r--doc/build/core/metadata.rst2
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/build/conf.py b/doc/build/conf.py
index 8f01adf86..ec9313678 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 bede2b00f..bf47a5b61 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 <https://alembic.readthedocs.io/>`_.
+by schema migration tools such as `Alembic <http://alembic.zzzcomputing.com/>`_.
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 8aece0b90..1e762b188 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 <https://alembic.readthedocs.io>`_ - Written by the author of SQLAlchemy,
+* `Alembic <http://alembic.zzzcomputing.com>`_ - 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