-
Type: Task
-
Resolution: Done
-
Affects Version/s: None
-
Component/s: None
-
None
If a model save fails because of database indexing/uniqueness constraints, it still returns true (and it seems the 'safely' function does not exist anymore?). Is there a way to prevent this?
This is in 3.0.22... please ignore if this is now unsupported.
Thanks!