Comments on: LINQ to SQL Generic Repository

By: Janus Knudsen

Janus Knudsen — Thu, 26 Nov 2009 22:00:37 +0000

IRepository is kinda mandatory when building assemblies/ layers, but your implementation into a common Repository is imho strange – you have to take some things for granted:
– PK will never be composite
– All entities have the same deletion and update constraints.

Just my 2 cent , but of course… if that is the intention, it’s a nice implementation.

By: Daniel Cotter

Daniel Cotter — Fri, 18 Sep 2009 20:09:25 +0000

I believe you’re missing a after IRepository in the first line:

public interface IRepository where T : class

It’s there in your sample code, but not on your web page.

By: Graham O'Neale

Graham O'Neale — Sat, 12 Sep 2009 10:45:53 +0000

@Anthony: No problem dude, glad to help

By: Anthony Gatlin

Anthony Gatlin — Sat, 12 Sep 2009 04:40:50 +0000

Your post was recommended by someone on stacked overflow as an answer to a question. Let me just say one thing. This is fabulous!!! It’s what I have been seeking for quite a while. Thank you so much for sharing it. Wow!

By: Graham O'Neale

Graham O'Neale — Mon, 03 Aug 2009 09:46:05 +0000

Very true
Yes I don’t mind a FindBy() call however as you can see I don’t mind traversing my IQueryable, so I am happy to use GetAll().Where(…) which let’s me use an out of the box filtering solution whenever I need it – LINQ. But for anything I might do more than once, I usually wrap this up into a business service, and that would call the LINQ query and return the enumerated result.

By: Joseph Ferris

Joseph Ferris — Fri, 31 Jul 2009 13:16:03 +0000

Nice write up. I have implemented something similar in our application architecture. The only real difference is that I have opted to move away from the IQueryable GetAll() approach for more fine-grained FindBy…() calls. Of course, this seems to represent two sides of a currently raging debate that we don’t need to reproduce here.