Unexpected reaction when using remove and saveChanges

[bstaley]

The documentation available for remove always calls saveChanges after calling remove. So I set it up like that and when invoked it would make two delete calls to the OData service. One after remove and one after saveChanges. For now I removed saveChanges and am only using remove. Is this the correct behavior?

[ogrim]

Are you calling remove on the Entity or the EntitySet? If you call remove directly on the Entity, the DELETE request will issue at once, and saveChanges is not needed.