I\'ve been reading about the sun blueprint GenericDAO implementation and Gavin King\'s take on this for use with Hibernate. It seems he doesn\'t mention anything about transaction handling:
I am trying to make changes to a site that uses SubSonic 2.0.3. I have all of the co开发者_运维知识库de but I need to regenerate some database tables. I do not have the SubCommander exe though. I look
I have a WCF svc separated into a Service Layer, Business Logic Layer and Data Access Layer. When my DAL encounters an exception, should I catch it there or let it bubble back up to the Service Laye
I know this could be opinion, but I\'m looking for best practices. As I understand, IQueryable<T> implements IEnumerable<T>, so in my DAL, I currently have method signatures like the foll
I have implemented Unity within my Asp.Net MVC2 project.I am currently registering my BLL types on Application Start.
In many posts concerning this topic I come across very simple examples that do not answer my question.
Which one can be开发者_开发问答 the better one data access component for desktop application and why?
Basically, DAL (Data Access Layer) should provide simple CRUD (Create/Read/Update/Delete) methods but I always have a temptation to create more sophisticated methods in order to minimize database acce
I am building a bug-tracking application, where I am thinking of taking maximum possible benefits of OOPS starting from my presentation layer to my data access layer. The architecture will be as usual
When communicating concurrency conflicts to your application layer, is there an alternative to using exceptions that also respects the principle of Command-Query Separation, or are exceptions the best
加载中,请稍侯......