0
 Followers
3
 Likes

Delete Action and Update action as counterpart of aggregate action

Backend
New

I would like to have two new actions one for deleting records and one for updating records.

Aggregates are great and preferred over using Advanced SQL.

For deleting and updating records (especially if there are a lot), for means of performance we use Advanced SQL. 

If we would have an action for delete and for update, where we have options like with an aggregate, to join and filter entities, and mark the entity which we want to update or delete, we could do more easily performant bulk updates and deletes.

This solves a the pattern of using an aggregate, foreach and delete<entity> which in many cases is just not performant enough. As it generates to many roundtrips to the database server.

Created on 11 Oct 2018
Comments (1)

Changed the category to Backend


views
212
Followers
0