A few posts back I wrote about the benefits of having a well encapsulated data access implementation. One of the benefits outlined there was the advantage it may bring when we need
When writing unit tests one of the challenges is to isolate your tests from everything. To isolate them from the code that is not in their target and also from the other
In my previous post I have presented a way to separate your data access from the business logic, when a relational database is used. I have shown another implementation of the well-known
In our days most of the applications that have a relational database as storage, use an ORM to access the data. The ORM (Entity Framework, Hibernate, etc.) does most of the data
You've successfully subscribed to Code Design
Great! Next, complete checkout to get full access to all premium content.
Welcome back! You've successfully signed in.
Success! Your account is fully activated, you now have access to all content.
Success! Your billing info is updated.
Error! Billing info update failed.