Don't forget to migrate with --database encrypted

Author: aclark4life

docs/howto/queryable-encryption.rst

@@ -198,7 +198,8 @@ Configuring the ``encrypted_fields_map``
 When you :ref:`configure an encrypted database connection
 <qe-configuring-databases-setting>` without specifying an
 ``encrypted_fields_map``, Django MongoDB Backend will create encrypted
-collections for you when you run ``python manage.py migrate``.
+collections for you when you run ``python manage.py migrate --database
+encrypted``.
 
 Encryption keys for encrypted fields are stored in the key vault
 :ref:`specified in the Django settings <qe-configuring-kms>`. To see the keys

docs/topics/queryable-encryption.rst

@@ -57,11 +57,11 @@ Django:
 
 
 Once you have defined your models, create the migrations with ``python manage.py
-makemigrations`` and run the migrations with ``python manage.py migrate``. Then
-create and manipulate instances of the data just like any other Django model
-data. The fields will automatically handle encryption and decryption, ensuring
-that :ref:`sensitive data is stored securely in the database
-<manual:qe-features-encryption-at-rest>`.
+makemigrations`` and run the migrations with ``python manage.py migrate
+--database encrypted``. Then create and manipulate instances of the data just
+like any other Django model data. The fields will automatically handle
+encryption and decryption, ensuring that :ref:`sensitive data is stored securely
+in the database <manual:qe-features-encryption-at-rest>`.
 
 Querying encrypted fields
 -------------------------