summaryrefslogtreecommitdiff
path: root/docs/build/cookbook.rst
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2018-11-26 22:42:28 -0500
committerMike Bayer <mike_mp@zzzcomputing.com>2018-11-26 22:42:28 -0500
commit54bd3ec824d96e0899396b4f953d89719bd9ca05 (patch)
treef830c4e6af9755ad75d9372b721ba490ef218e72 /docs/build/cookbook.rst
parent804d1d420bb8abfceb2cde46321fd5fa3dde357e (diff)
downloadalembic-54bd3ec824d96e0899396b4f953d89719bd9ca05.tar.gz
Move to github, new domain, sqlalchemy links
Alembic is now under the sqlalchemy.org domain for the website and all repos are moving under github.com/sqlalchemy. Change-Id: Id9ce08b61ed0ccdf50396f911838b21112e61652
Diffstat (limited to 'docs/build/cookbook.rst')
-rw-r--r--docs/build/cookbook.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/build/cookbook.rst b/docs/build/cookbook.rst
index ffa05a3..4ace79e 100644
--- a/docs/build/cookbook.rst
+++ b/docs/build/cookbook.rst
@@ -294,7 +294,7 @@ The Replaceable Object Structure
We first need to devise a simple format that represents the "CREATE XYZ" /
"DROP XYZ" aspect of what it is we're building. We will work with an object
that represents a textual definition; while a SQL view is an object that we can define
-using a `table-metadata-like system <https://bitbucket.org/zzzeek/sqlalchemy/wiki/UsageRecipes/Views>`_,
+using a `table-metadata-like system <https://github.com/sqlalchemy/sqlalchemy/wiki/UsageRecipes/Views>`_,
this is not so much the case for things like stored procedures, where
we pretty much need to have a full string definition written down somewhere.
We'll use a simple value object called ``ReplaceableObject`` that can