Comments on: Creating a Data Access Layer with Linq to SQL, part 1 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/ Kris Vandermotten's blog Sat, 09 May 2009 00:04:07 +0000 http://wordpress.com/ hourly 1 By: mikew909 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-2613 mikew909 Thu, 15 May 2008 03:30:41 +0000 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-2613 Hiya - great article you got me rethinking about DALs now, I've been dabbling in ORM applications like EntitySpaces and LLBLGen but I'm going to investigate LINQ some more cheers :) Hiya – great article you got me rethinking about DALs now, I’ve been dabbling in ORM applications like EntitySpaces and LLBLGen but I’m going to investigate LINQ some more

cheers :)

]]> By: AlanLe.net » links for 2008-04-03 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-2608 AlanLe.net » links for 2008-04-03 Thu, 03 Apr 2008 08:36:54 +0000 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-2608 [...] Creating a Data Access Layer with Linq to SQL, part 1 « Kris.NET (tags: data linq) [...] [...] Creating a Data Access Layer with Linq to SQL, part 1 « Kris.NET (tags: data linq) [...]

]]> By: Stiiifff http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-2596 Stiiifff Mon, 28 Jan 2008 08:54:24 +0000 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-2596 Hi Kris, You might have a look about what is named by Ayende as 'Partial Domain Models': http://ayende.com/Blog/archive/2008/01/12/Creating-Partial-Domain-Models.aspx http://blog.yoot.be/2008/01/partial-domain-models-and-more.html In that case, the ORM is NHibernate ... but the problem remains the same. IMHO, the fact that Linq to SQL force you to have all your domain model expressed in one file per database doesn't mean that you have to go that way, especially when you would have liked to split your domain model in several sub-models. If you put all your entities in one big domain model, you end up trying to re-split the whole model in a higher layer. Another interesting option is to use the Repository pattern, defined by a generic interface exposing Queryable collection so that you can use Linq for all your queries. The actual implementation of the Repository being Linq to SQL, or any other ORM ... it is less important as the Repository is actually abstracting your service layer, using Linq queries, from the actual 'Data Layer'. Check this article: http://andrewpeters.net/2007/04/28/fixing-leaky-repository-abstractions-with-linq Steve Hi Kris,

You might have a look about what is named by Ayende as ‘Partial Domain Models’:
http://ayende.com/Blog/archive/2008/01/12/Creating-Partial-Domain-Models.aspx
http://blog.yoot.be/2008/01/partial-domain-models-and-more.html
In that case, the ORM is NHibernate … but the problem remains the same.

IMHO, the fact that Linq to SQL force you to have all your domain model expressed in one file per database doesn’t mean that you have to go that way, especially when you would have liked to split your domain model in several sub-models. If you put all your entities in one big domain model, you end up trying to re-split the whole model in a higher layer.

Another interesting option is to use the Repository pattern, defined by a generic interface exposing Queryable collection so that you can use Linq for all your queries. The actual implementation of the Repository being Linq to SQL, or any other ORM … it is less important as the Repository is actually abstracting your service layer, using Linq queries, from the actual ‘Data Layer’.

Check this article:
http://andrewpeters.net/2007/04/28/fixing-leaky-repository-abstractions-with-linq

Steve

]]> By: progrmr http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-2563 progrmr Wed, 16 Jan 2008 14:27:35 +0000 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-2563 I agree with the blog. There are certainly many ways to arrange things but I'm doing pretty much the exact same thing. My LinqToSql schema represents the entire database and seperate entity classes utilize that single data context. Good blog - onto part 2. I agree with the blog. There are certainly many ways to arrange things but I’m doing pretty much the exact same thing. My LinqToSql schema represents the entire database and seperate entity classes utilize that single data context.

Good blog – onto part 2.

]]> By: Adam Schaible http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-2336 Adam Schaible Tue, 08 Jan 2008 01:20:15 +0000 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-2336 cumpsd: I'm faced with a similar situation - here's my solution. Interface the DAO's, and make your implementation use Linq - create a static service layer that wraps all of your DAO's, and it's kind of like the "DAL" if you will. All of your code will call this static service layer, that references the linq implementations by their interface type. cumpsd:

I’m faced with a similar situation – here’s my solution.

Interface the DAO’s, and make your implementation use Linq – create a static service layer that wraps all of your DAO’s, and it’s kind of like the “DAL” if you will. All of your code will call this static service layer, that references the linq implementations by their interface type.

]]> By: cumpsd http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-902 cumpsd Wed, 22 Aug 2007 20:08:36 +0000 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-902 I'm favored into thinking that linq *is* the DAL, but in the business I'm currently working on, there's need for higher flexibility. What do I mean with that? I'll be going for an architecture (haven't finished it yet) which uses LINQ for all it's data access, but all the layers above that shouldn't know that linq is running under the hood. The reason for this, it's very possible there comes a point during early stages of development where votes are against linq and I have to take it out again, replacing it by something else. At that point, I really don't want to rewrite anything above the data layer. Does Linq bind us too much into choosing 1 solution for our data? I’m favored into thinking that linq *is* the DAL, but in the business I’m currently working on, there’s need for higher flexibility.

What do I mean with that? I’ll be going for an architecture (haven’t finished it yet) which uses LINQ for all it’s data access, but all the layers above that shouldn’t know that linq is running under the hood.

The reason for this, it’s very possible there comes a point during early stages of development where votes are against linq and I have to take it out again, replacing it by something else.

At that point, I really don’t want to rewrite anything above the data layer.

Does Linq bind us too much into choosing 1 solution for our data?

]]> By: All you can LINQ » Sending the LINQ to SQL log to the debugger output window http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-790 All you can LINQ » Sending the LINQ to SQL log to the debugger output window Tue, 31 Jul 2007 22:21:02 +0000 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-790 [...] a series of posts about the impact the use of LINQ to SQL has over a classical Data-Access Layer (part 1, part [...] [...] a series of posts about the impact the use of LINQ to SQL has over a classical Data-Access Layer (part 1, part [...]

]]> By: fluxcapacity » Blog Archive » Data Access Layer: To LINQ or not to LINQ http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-777 fluxcapacity » Blog Archive » Data Access Layer: To LINQ or not to LINQ Sat, 21 Jul 2007 22:11:51 +0000 http://krisvandermotten.wordpress.com/2006/11/19/creating-a-data-access-layer-with-linq-to-sql-part-1/#comment-777 [...] introduction, and Kris Vandermotten shares some thoughts on LINQ’s implications on the DAL here and here.  He writes: There is no doubt that Linq to SQL will have an enormous impact on the way [...] [...] introduction, and Kris Vandermotten shares some thoughts on LINQ’s implications on the DAL here and here.  He writes: There is no doubt that Linq to SQL will have an enormous impact on the way [...]

]]>