Changes between Initial Version and Version 1 of Ticket #34944
- Timestamp:
- Nov 5, 2023, 4:31:39 AM (14 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #34944 – Description
initial v1 3 3 I do not rule out that there are other examples of use of the generated fields that could lead to the same errors and if they come to mind, please add them in the comments. 4 4 5 == Misinferred attributes5 === Misinferred attributes 6 6 7 7 In the common example of a field generated as a concatenation of two CharField in a Model: … … 44 44 45 45 46 == Missing attributes46 === Missing attributes 47 47 48 48 If in the previous example, I explicitly specify the output field without attributes, the migration is generated without generating errors: … … 93 93 b. request to specify mandatory attributes for the output fields raising an error in the migration creation phase 94 94 95 == Cumulative proposal95 === Cumulative proposal 96 96 97 97 To solve both problems shown above, given the little time remaining before the release of the stable version of Django 5, the two most drastic solutions from both of the above proposals could be adopted.