It steps through what has changed in the field and generates SQL for the database relevant changes, queueing up statements with self.execute. Any non-SQL changes are basically ignored.
On Sat, Sep 30, 2023, at 3:57 PM, Akash Sen wrote:
Hello everyone,
There are certain attributes in a field, after changing these the migration generated willbe applied to database, (for example take foreignkey) like null=True or db_default=1. As they have something to do with the database column.
There are some other attributes after changing these the migration generated will not be applied to database, like on_delete. As currently they have nothing to do with the database column.
In search of the code that takes care of that. Some help would be great!
--
You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group.