Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Some software currently being written has a requirement for the data model to be transactional, implementing CRUD operations. (get a copy of data, make changes, submit it atomically, get fault messages for failures, etc.)
Is there a well documented design pattern for something like this? Maybe a library?
NOTE: I’m using C#/.NET 4.0
PLEASE NOTE, my data model is POCO! not SQL or anything.
Use an ORM like Entity Framework, nHibernate etc
They have built in change tracking system and implement “Unit of Work” pattern(single transaction)