Retrieve then Delete - optimization

Hi all, I know that Mendix optimizes retrieve and aggregate actions where possible - Does anybody know if the same is true if I do a retrieve and then a delete? It seems redundant to retrieve all the data just to be able to delete the object. If it is not optimized then is there another way to delete object without retrieving them? -Andrej
1 answers

I don't have the answer, but did you try logging on trace level to see what database calls are performed? Perhaps this gives some insight.