search

jaystack / jaydata

Notice: this library isn't maintained anymore
http://jaydata.org
GNU General Public License v2.0
352 stars 95 forks source link

Unexpected reaction when using remove and saveChanges #288

Open bstaley opened 7 years ago

bstaley commented 7 years ago

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 commented 6 years ago

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.