data mapper pattern
up until i've controlling active annals c# database driven applications. nonetheless concentration requires attention formula being separate business objects. i have review lot posts per martin fowler's information mapping pattern, nonetheless trust settlement still unequivocally limited.
let's following example:
if i have 2 tables - fan customerparameters. customerparameters list contains default fan values formulating new customer.
i following have emanate customersmapper category hoop fan persistence. fan customerslist category following combine mapper category method insist fan data.
i have following questions:
how i send tender information & fan category mapper but defilement certain business rules? dto's?
is tolerable have saveall loadall slight mapper category updating loading churned customers' data? so, box saveall, mapper know transform insert data?
will fan mapper category grateful retrieving default values customerparameters list well, improved emanate customerparameters mapper?
a o/r mapper apparatus unequivocally here. database i'm controlling transactional requires i possess mapper pattern.
any ideas comments severely appreciated.
Comments
Post a Comment