Comments on: LINQ to SQL and Entity Framework as Internal Object Databases http://wizardsofsmart.net/patterns/linq-to-sql-and-entity-framework-as-internal-object-databases/ .NET Design Patterns Fri, 25 Jun 2010 20:49:03 +0000 hourly 1 http://wordpress.org/?v=3.1-alpha By: Dennison Uy http://wizardsofsmart.net/patterns/linq-to-sql-and-entity-framework-as-internal-object-databases/comment-page-1/#comment-9 Dennison Uy Tue, 12 May 2009 04:00:07 +0000 http://wizardsofsmart.net/?p=118#comment-9 @Riles I suggest looking into Castle Project's ActiveRecord, which is built on top of NHibernate @Riles I suggest looking into Castle Project's ActiveRecord, which is built on top of NHibernate

]]> By: riles http://wizardsofsmart.net/patterns/linq-to-sql-and-entity-framework-as-internal-object-databases/comment-page-1/#comment-8 riles Sat, 28 Mar 2009 13:54:11 +0000 http://wizardsofsmart.net/?p=118#comment-8 Ben, you make an excellent point, and one I've conceded to JB, as well. I hadn't thought of it in terms of the Proxy pattern previously, but that's certainly a valid reason. I've also come around to enjoying "Fluent NHibernate":http://fluentnhibernate.org/. Ben, you make an excellent point, and one I’ve conceded to JB, as well. I hadn’t thought of it in terms of the Proxy pattern previously, but that’s certainly a valid reason. I’ve also come around to enjoying “Fluent NHibernate”:http://fluentnhibernate.org/.

]]> By: Ben Scheirman http://wizardsofsmart.net/patterns/linq-to-sql-and-entity-framework-as-internal-object-databases/comment-page-1/#comment-7 Ben Scheirman Tue, 17 Mar 2009 19:23:06 +0000 http://wizardsofsmart.net/?p=118#comment-7 I don't mind making my entities virtual if I intend to fully take advantage of lazy loading. But virtual != persistence concern. It's just a fact that that my persistence strategy needs that if I am to use lazy loading. I'm not inheriting a base class or cluttering my class with attributes. I'm simply opening up my class for extension. That's not a persistence concern. I don’t mind making my entities virtual if I intend to fully take advantage of lazy loading. But virtual != persistence concern.

It’s just a fact that that my persistence strategy needs that if I am to use lazy loading.

I’m not inheriting a base class or cluttering my class with attributes. I’m simply opening up my class for extension. That’s not a persistence concern.

]]>