Changes between Initial Version and Version 1 of Ticket #28222
- Timestamp:
- May 18, 2017, 10:10:27 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #28222 – Description
initial v1 1 This is an issue related to #27118. Anthony King commented on it but that issue is closed so I am opening a new one. The field validation introduced in 1.11 `update_or_create` will throw a FieldErrorif a `defaults` argument contains a value that is set through an `@property.setter` on that model. On the other hand `create` continues to function correctly. Ideally they'd behave consistently.1 This is an issue related to #27118. Anthony King commented on it but that issue is closed so I am opening a new one. The field validation introduced in 1.11 `update_or_create` will throw a `FieldError` if a `defaults` argument contains a value that is set through an `@property.setter` on that model. On the other hand `create` continues to function correctly. Ideally they'd behave consistently. 2 2 3 3 Here is an example https://dpaste.de/UORC