Thanks for your reply, Tom. Just now I found the problem. From my SO answer...
`cid` must be set to readonly, and then the URL for PUT/PATCH is correctly formed. So now I'm mutating the `read_only_fields` in the viewset `get_serializer_class` so I can set the `cid` field on POST, but be readonly on PUT/PATCH. That gets me up and going, but there will be (infrequent) times when the `cid` value must change, and I don't know what the thing will be to do then. :'‑( Why must a `lookup_field` be readonly? If it's incorrect and unworkable to have a `lookup_field` be writable, an error message would be very helpful, instead of the current behavior. On Wednesday, June 7, 2017 at 7:54:39 AM UTC-4, Tom Christie wrote: > > I'll try to have a look in details at the issue over the next day or two, > but yes coreapi does support all the HTTP methods, so the problem is > likely something else. > -- You received this message because you are subscribed to the Google Groups "Django REST framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
