summaryrefslogtreecommitdiff
path: root/doc/build/core
diff options
context:
space:
mode:
authorAdam Chainz <adam@adamj.eu>2016-05-29 14:28:55 +0100
committerAdam Chainz <adam@adamj.eu>2016-05-29 14:28:55 +0100
commit513a045395b4cb5d8e1a9deb69bc9761d79eee37 (patch)
tree5ff66efc419b1bec9f2d08bf0931e85da30a5ebb /doc/build/core
parent4856493efc1f6b7fdecf36e020a95636f600a626 (diff)
downloadsqlalchemy-pr/278.tar.gz
Convert readthedocs link for their .org -> .io migration for hosted projectspr/278
As per their email ‘Changes to project subdomains’: > Starting today, Read the Docs will start hosting projects from subdomains on the domain readthedocs.io, instead of on readthedocs.org. This change addresses some security concerns around site cookies while hosting user generated data on the same domain as our dashboard. Test Plan: Manually visited all the links I’ve modified.
Diffstat (limited to 'doc/build/core')
-rw-r--r--doc/build/core/constraints.rst2
-rw-r--r--doc/build/core/metadata.rst2
2 files changed, 2 insertions, 2 deletions
diff --git a/doc/build/core/constraints.rst b/doc/build/core/constraints.rst
index 197eeb8a9..bede2b00f 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 <http://http://alembic.readthedocs.org/>`_.
+by schema migration tools such as `Alembic <https://alembic.readthedocs.io/>`_.
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 b37d579f1..8aece0b90 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 <http://alembic.readthedocs.org>`_ - Written by the author of SQLAlchemy,
+* `Alembic <https://alembic.readthedocs.io>`_ - 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