where put additional functionality database covering (linq-to-sql)


what best slight exercise additional functionality database covering uses linq-to-sql? now i'm looking during implementing functions adding information formed presets identical tasks?



inserts, updates deletes requires opening datacontext table classes don't have opening context. i've seen solutions uses singletons nonetheless seems penetrate i awe anyone else run problem your solutions were? there improved proceed together exercise identical functionality.



the reason me looking supplement functionality database covering i have several applications same database objects i wish means functions applications i don't have rewrite lot code.






that's definitely i meant. i wish means challenging actions updating list adding record another list formed information initial one.



say i have comparison fan record i wish transform information, happens i wish supplement another record "updates" list keep lane updates happened them. wholly an instance course. things indispensable finished some-more complex.



basically i wish supplement slight list vigilant perform modifications specific quarrel list following inserts updates objects. i know biased classes i extensively already.



example:



db.customers.where(c => c.customerid == 5).addorder(orderdetails);


i feel i can't unequivocally put problem difference graphic :)



Comments

Popular posts from this blog

list macos calm editors formula editors

how i practical urls indicate .aspx pages asp.net deployed an iis? (preferably but iis)

jaxb - xjc - reworking generated typesafe enum category members