Changes between Initial Version and Version 1 of Ticket #34944, comment 14
- Timestamp:
- Nov 7, 2023, 8:10:20 PM (11 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #34944, comment 14
initial v1 1 1 Resolving the `output_field` of combined expressions is a complex task that the ORM only has limited support for #26355, #31506, #33397, this is not a problem specific to `GenerateField`. 2 2 3 It is particularly tricky in the case of `varchar(x) + varchar(y)` as some backends restrict the allowed length of `varchar` (e.g. MySQL a s255) and using a `TextField` might come with backend specific limitations.3 It is particularly tricky in the case of `varchar(x) + varchar(y)` as some backends restrict the allowed length of `varchar` (e.g. MySQL at 255) and using a `TextField` might come with backend specific limitations. 4 4 5 Our stance so far has been to make a best effort guess and [https://docs.djangoproject.com/en/4.2/ref/models/expressions/#output-field refuse the temptation to guess otherwise].5 Our stance so far has been to make a best effort guess and [https://docs.djangoproject.com/en/4.2/ref/models/expressions/#output-field refuse the temptation to guess]. 6 6 7 7 I suggest that we take the same approach here and expect the user to specify an explicit `output_field`.