Not quite. If you run python manage.py sqlmigrate <appname> <migration_name>, you can see the SQL generated for that migration.
https://docs.djangoproject.com/en/2.0/ref/django-admin/#django-admin-sqlmigrate Because Django emulates Cascade, its done outside of the db, and therefore shouldn't be a db-level constraint. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/161fe559-0aa4-4386-b6c7-67d231c6dd4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
