💡 update README to clarify legacy behavior of SQLite views option

Author: techouse

README.md

@@ -45,6 +45,9 @@ Options:
                                   Implies --without-foreign-keys which
                                   inhibits the transfer of foreign keys. Can
                                   not be used together with --sqlite-tables.
+  -A, --sqlite-views-as-tables    Materialize SQLite views as tables in MySQL
+                                  instead of creating matching MySQL views
+                                  (legacy behavior).
   -X, --without-foreign-keys      Do not transfer foreign keys.
   -W, --ignore-duplicate-keys     Ignore duplicate keys. The default behavior
                                   is to create new ones with a numerical

docs/README.rst

@@ -36,6 +36,7 @@ Transfer Options
 
 - ``-t, --sqlite-tables TUPLE``: Transfer only these specific tables (space separated table names). Implies ``--without-foreign-keys`` which inhibits the transfer of foreign keys. Can not be used together with ``--exclude-sqlite-tables``.
 - ``-e, --exclude-sqlite-tables TUPLE``: Exclude these specific tables (space separated table names). Implies ``--without-foreign-keys`` which inhibits the transfer of foreign keys. Can not be used together with ``--sqlite-tables``.
+- ``-A, --sqlite-views-as-tables``: Materialize SQLite views as tables in MySQL instead of creating matching MySQL views (legacy behavior).
 - ``-E, --mysql-truncate-tables``: Truncates existing tables before inserting data.
 - ``-K, --mysql-skip-create-tables``: Skip creating tables in MySQL.
 - ``-i, --mysql-insert-method [UPDATE|IGNORE|DEFAULT]``: MySQL insert method. DEFAULT will throw errors when encountering duplicate records; UPDATE will update existing rows; IGNORE will ignore insert errors. Defaults to IGNORE.