Saving aggregate about domain-driven-hexagon

[Sairyss]

TypeOrm save and update methods support partial updating (meaning that it discards all undefined properties). You can create an update method in your repository that accepts something like Partial<Entity> and updates only those fields you need it to update.
Anyway, I don't think this is something you should worry about that much. Updating a single aggregate by multiple request should not happen often. Most of your aggregates are probably updated by a single user anyway and in most cases users are not sending requests that fast.
I'd recommend spending time on a solution only if you have a real bottleneck in your application that is causing problems, otherwise don't worry about it.

[Sairyss]

Good point.
TypeOrm repositories provide an update() so it would be safer to use that instead.
Will fix it in the future if I have time

[cosinus84]

Thanks for your quick answer, but if we look more general.... aggregate saving, the whole aggregate (all stackoverflow and other articles on the web out there), is fishy for me :).

Basically for this to work you shoud mix repository with logic, as in standard module->controller->service. Otherwise keeping logic in aggregate only you should "tell" somehow to the repository to save the exact fields that needs to update, maybe rows to insert, delete. Do you have some suggestion on this ?