Relationship not included in payload on PUT about spine HOT 3 CLOSED

Because Spine doesn't support client side ids, SaveOperation simply looks at the id field to check whether it should be a POST or PUT.

The reason that relationships are not included on PUT requests is because we can't be sure whether a relationship has been fetched from the server in the first place. If you fetch a resource without relationship data, change an attribute and then save it including the empty relationship data, the relationships would be overwritten with empty data (and thus lost).

I don't think we can easily work around this, unless we add dirty checking or do a lot of bookkeeping on which attributes were fetched. If you have a different solution for this project, I'm happy to integrate it. However, if it's a big change it might be better to hold off on this until we converted to Swift 2.0.

from spine.

Ok. I added category_id to my data.attributes to get it done (I own the server, so...). Not good but it'll work for now. As for client side ids, I agree, it's doing PUTs and I have to do some work on the server.

from spine.

I'm closing this issue in favour of the Client side ids issue: #37. When client side ids are implemented, this should be resolved as well.

from spine.