Akash Kumar Sen

Thank you for the suggestions @LilyFoote . Updated the patch with the follwing : - Reduced the number of queries to exactly 1. - Optimized the logic inside the nested...

- Added tests for migrations. **There are two issues I could not figure out after a lot of try, some help would be great :** - MySQL specific error in...

> Firstly, this is not where I think it is failing. To me it looks like it is struggling to create the table `DBDefaultsFK` (`delete_dbdefaultsfk`) which is in `tests/delete/models.py` (when...

> @Akash-Kumar-Sen I think go for the disabling MySQL support plan (also needs a docs adjustment). Done @sarahboyce .

> @Akash-Kumar-Sen Do you have some failing tests you can push? @LilyFoote here is a failing test. https://github.com/django/django/blob/ceb6dafb82a8d328f3324bb4357812e2ab5ba40c/tests/migrations/test_operations.py#L244

> I also think we might need to take a different approach to the `subTest`s, to allow us to cleanly test the backwards migrations also do the right thing. >...

I will make this more exhaustive following your suggestions. > I'm not really sure. Maybe there's a way to have a group of asserts associated with each on_delete option, and...

I want to work on this issue!

I want to work on this issue!