Changes between Initial Version and Version 1 of Ticket #33441, comment 7
- Timestamp:
- Jan 14, 2022, 2:31:42 AM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #33441, comment 7
initial v1 1 1 > Could you go into more detail about this statement? Fields meant to be assigned/bound to a model class should all be set after the app setup phase and no fields should be bound to a model class after this point so I'm struggling to come up with the plenty of uses in ORM expressions you are referring to. Just saying that providing concrete examples might help your case here. 2 2 3 > 3 > I'm also struggling with finding "plenty of uses", nevertheless it should not block this change . 4 4 5 5 Sorry, I wasn't clear. I meant: There are plenty of uses for fields in ORM expressions. These *might* lead a user to create references to a field before/after they are assigned to a model class. I don't have a concrete example, and clearly it must be rare, since no one has reported a bug since Django 3.2. But, I don't think it's inconcievable that someone will try this at some point.