Changes between Initial Version and Version 1 of Ticket #30774
- Timestamp:
- Sep 13, 2019, 12:37:52 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #30774 – Description
initial v1 1 1 When using Enum object as a default value for a CharField, the generated migration file uses the value of the Enum object instead of the its name. This causes a problem when using Django translation on the value of the Enum object. 2 2 3 The problem is that, when the Enum object value get translated to the users language, the migrations raise an error stating that the Enum does not have the corresponding value. (because the Enum value is translated to another language)3 The problem is that, when the Enum object value get translated to the users language, the old migration files raise an error stating that the Enum does not have the corresponding value. (because the Enum value is translated to another language) 4 4 5 5 Example: