Repository Pattern with NPoco, Worth it?

I am considering NPoco for a large business application. I am a bit concerned that is it worth to develop a repository pattern?

I will need to handle complex SQL statements and extensive database operations on several entities in a same use case.

NPoco provides a variety of db operations functions, which I think will not be (directly) exposed to the consumer layer(s) by my repository layer.

Edit-1 Which approach is better to get most out of NPoco?


If you want to invest time in unit tests, then the Repository Pattern is worth it. However if most of your application logic is in stored procs and functions, then you will be limited with unit tests and just spend your time in integration testing.

Need Your Help

Chart requirement for an application

charts gantt-chart

Am working on an application that has a requirement like, All the tasks has to be represented in a gantt view with milestones and critical path. Chart should also show the analysis of Baseline vs A...

Some basic questions about debugging core files C++/linux?

c++ debugging memory-leaks gdb core

Debugging files of C++ applications/linux have always been a mystery to me and some basic understanding is lacking.