diff options
author | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-11-30 19:03:06 -0500 |
---|---|---|
committer | Mike Bayer <mike_mp@zzzcomputing.com> | 2014-11-30 19:03:06 -0500 |
commit | effb8e12bb2c32d3f54c0c3d6e9798a2c43e4a4c (patch) | |
tree | 6d71e622bf0ba75e80ba7879b5792f84a1c4e35d | |
parent | 735889f068c58f8a278dcfe5bda7496624339026 (diff) | |
download | alembic-effb8e12bb2c32d3f54c0c3d6e9798a2c43e4a4c.tar.gz |
- reword the first paragraph about offline mode to better flow
from the preceding sections.
-rw-r--r-- | docs/build/batch.rst | 12 |
1 files changed, 7 insertions, 5 deletions
diff --git a/docs/build/batch.rst b/docs/build/batch.rst index c48fe64..04a32c4 100644 --- a/docs/build/batch.rst +++ b/docs/build/batch.rst @@ -219,11 +219,13 @@ users. Working in Offline Mode ----------------------- -Another big limitation of "move and copy" is that in order to make a copy -of a table, the structure of that table must be known. -:meth:`.Operations.batch_alter_table` by default will use reflection to -get this information, which means that "online" mode is required; the -``--sql`` flag **cannot** be used without extra steps. +In the preceding sections, we've seen how much of an emphasis the +"move and copy" process has on using reflection in order to know the +structure of the table that is to be copied. This means that in the typical +case, "online" mode, where a live database connection is present so that +:meth:`.Operations.batch_alter_table` can reflect the table from the +database, is required; the ``--sql`` flag **cannot** be used without extra +steps. To support offline mode, the system must work without table reflection present, which means the full table as it intends to be created must be |