The "Commanders" are needed where a single SQL operation is faster than a
classic ORM approach. Let's say we have a table called PRODUCTS and we need to
apply a discount of 20% on all products. Using the current implementation I've
to load all the products, applica the discount and then save them one by one.
This is the corrent way to to things if there are consistency check o validity
check implemented in the object, but is there aren't validity check, I need a
faster way. A commander is for an UPDATE/DELETE/INSERT what a finder id for
SELECT.
Will be used in the same way but do not return any lists.
Session.Execute(TApplyGlobalDiscount.Create(20));
Original issue reported on code.google.com by daniele....@gmail.com on 3 Jan 2012 at 1:57
Original issue reported on code.google.com by
daniele....@gmail.com
on 3 Jan 2012 at 1:57