From: Mike Bayer Date: Mon, 1 Dec 2014 00:03:06 +0000 (-0500) Subject: - reword the first paragraph about offline mode to better flow X-Git-Tag: rel_0_7_1~7 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=effb8e12bb2c32d3f54c0c3d6e9798a2c43e4a4c;p=thirdparty%2Fsqlalchemy%2Falembic.git - reword the first paragraph about offline mode to better flow from the preceding sections. --- diff --git a/docs/build/batch.rst b/docs/build/batch.rst index c48fe646..04a32c4b 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