Does DRF CreateModelMixin break atomicity?

[APCBoston]

According to the DRF documentation, serializers should be expected to both create a model object and save to the db, by using a .save() call or .objects.create(). However, the create-validate-save flow implemented in CreateModelMixin leaves open the possibility that a POST call to create an object will fail (that is, will not return 201), even though the requested object has been created and saved to the db.

Granted, it appears that this would only happen if the serializer-created object fails serializer-validation, which shouldn't happen.

[APCBoston]

A colleague has helped me to find my error here. I had believed that the serializer's __init__ method would call create(), but this is not so -- despite the intuitive appeal of the constructor being the place where "create" happens, that in fact occurs in save(), which entirely moots my concern.