summaryrefslogtreecommitdiff
path: root/docs/build/tutorial.rst
diff options
context:
space:
mode:
authorMike Bayer <mike_mp@zzzcomputing.com>2014-11-09 16:27:11 -0500
committerMike Bayer <mike_mp@zzzcomputing.com>2014-11-09 16:27:11 -0500
commit713b128df48ba4ea638bb34b563bcfe10bbcf16f (patch)
tree0011fe565120e2daf6a3daf39fb4a7b28db39a50 /docs/build/tutorial.rst
parent36fa6e4603ba19d6c27b4e4c728a30effa72fdc0 (diff)
downloadalembic-713b128df48ba4ea638bb34b563bcfe10bbcf16f.tar.gz
- changelogbatch_alter
fixes #21
Diffstat (limited to 'docs/build/tutorial.rst')
-rw-r--r--docs/build/tutorial.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/build/tutorial.rst b/docs/build/tutorial.rst
index a4ae517..016e81b 100644
--- a/docs/build/tutorial.rst
+++ b/docs/build/tutorial.rst
@@ -930,7 +930,7 @@ to be changed.
Migration tools are instead expected to produce copies of SQLite tables that
correspond to the new structure, transfer the data from the existing
table to the new one, then drop the old table. For our purposes here
-we'll call this **"move and copy" workflow**, and in order to accommodate it
+we'll call this **"move and copy"** workflow, and in order to accommodate it
in a way that is reasonably predictable, while also remaining compatible
with other databases, Alembic provides the **batch** operations context.