Re: [Django] #37348: Removing null=True from GeneratedField should be a SQL no-op (was: Removing `null=True` from GeneratedField should be a SQL no-op)

[Django]

#37348: Removing null=True from GeneratedField should be a SQL no-op
-------------------------------------+-------------------------------------
Reporter: Michal Porteš | Owner: (none)
Type: Bug | Status: new
Component: Database layer | Version: 6.1
(models, ORM) |
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Sarah Boyce):

* severity: Normal => Release blocker
* stage: Unreviewed => Accepted
* summary: Removing `null=True` from GeneratedField should be a SQL no-op
=> Removing null=True from GeneratedField should be a SQL no-op

Comment:

Thank you for the report!
I think ideally there would be no migration at all
I am also wondering if #36806 should be mentioned in the 6.1 release notes
--
Ticket URL: <https://code.djangoproject.com/ticket/37348#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.