Ian Cooper [MVP] - All Comments

re: Architecting LINQ To SQL Applications, part 7

Mike — Thu, 15 May 2008 18:46:21 GMT

Hi Ian

I am really enjoying your articles on Linq to SQL - particularly the discussion about DataContext and layers.

I have plans to teach a first year undergrad web dev. course based on Linq to SQL in September and I have been struggling with these issues for a while ......

You mentioned that Linq to SQL has a similar pattern using DataContext to Paul Wilson's ORM (WORM) and perhaps you could explain that it more detail. I have used WORM for many years in development and in teaching and thought I understood it - but I am struggling with Linq to SQL DataContext as I can't seem to hide it - in the same way that WORM hides its equivalent.

WORM was ideal for students as I could hide all the ORM detail in the DAL and gradually expose parts as required (from a teaching perpective) but am finding this hard with DataContext

Thanks again

Mike

Architecting LINQ to SQL applications - by Ian Cooper

Gerlei Márton blogja az Architektúra Fórumon — Wed, 07 May 2008 21:55:07 GMT

Egy LINQ-s problémával küszködve találtam az alábbi cikksorozatot, és szerintem eléggé hasznos. Sok mindenről

Architecting LINQ to SQL applications - by Ian Cooper

Gerlei Márton blogja az Architektúra Fórumon — Wed, 07 May 2008 21:54:54 GMT

Egy LINQ-s problémával küszködve találtam az alábbi cikksorozatot, és szerintem eléggé hasznos. Sok mindenről

re: Architecting LINQ To SQL Applications, part 8

mike — Sat, 03 May 2008 20:51:57 GMT

Any idea when you might have part 9 ready?

best practices for rdbms

best practices for rdbms — Thu, 24 Apr 2008 11:28:05 GMT

Pingback from best practices for rdbms

The role of Architect in Software Development

Bryan Hinton's Blog — Wed, 16 Apr 2008 21:44:06 GMT

Two good articles below that explore what an architect really means in the world of software development

re: Architecting LINQ to SQL applications, part 3

Mohammad Azam — Fri, 11 Apr 2008 19:07:30 GMT

Hi,

So, how are you initializing the DataContext and from where are you sending the context.

public class NorthwindRepository

{

private IQueryable<Customer> customers;

public NorthwindRepository(DataContext context)

{

customers = context.GetTable<Customer>();

}

public Customer FindCustomer(string customerId)

{

return (from c in customers

where c.CustomerID == customerId

select c).Single<Customer>();

}

re: Architecting LINQ To SQL Applications, part 7

Daniel Fernandes — Fri, 11 Apr 2008 12:46:41 GMT

Features I see that are "obviously" missing from Linq To Sql (hand coded or not) are:

- no support of polymorphism for associations, CRUD and queries, at least with the generated code, I guess you can have polymorphic associations with hand coded mapping but that needs to be confirmed.

- Lack of support to clearly configure cascade behaviour for either create, update or deletes (it's my view that deletions should be handled by code near the domain model and not within the db).

- Inability to create custom types built from sql datatypes.

- No clean way to intercept calls to the db. On generated code one has to use partial methods to handle this, not sure how it would works for hand coded and I'm not sure how the GetChangeSet() command actually works, does it return the full set of entities that are going to be affected by the unit of work including entities that will be updated due to cascade ?

To me the one little gem in NHibernate is support of Many to Any relationship where something on the Many side can be linked to literally anything on the other side using a table in the middle providing all the necessary configuration to act as an object factory.

PS: I still do very much appreciate your series, I tried to do this very architecture with NHibernate but it didn't quite work out, DDD was confusing me on a daily basis..!

Daniel

weekend breaks in scotland

weekend breaks in scotland — Fri, 11 Apr 2008 07:41:57 GMT

Pingback from weekend breaks in scotland

find the best web designer

find the best web designer — Thu, 10 Apr 2008 10:07:20 GMT

Pingback from find the best web designer

http://nhibernate.codebetter.com/blogs/ian_cooper/archive/2007/12/04/architecting-linq-to-sql-applications-part-4.aspx

Wed, 09 Apr 2008 15:53:29 GMT

Pingback from nhibernate.codebetter.com/.../architecting-linq-to-sql-applications-part-4.aspx

re: Architecting LINQ to SQL applications, part 4

Scott Wojan — Wed, 09 Apr 2008 13:13:04 GMT

Ian,

Not sure if you are familiar with the criteria api in NHibernate but it allows compile time checking for querying objects:

www.hibernate.org/.../querycriteria.html

best xml software

best xml software — Tue, 08 Apr 2008 19:17:16 GMT

Pingback from best xml software

http://development.codebetter.com/blogs/ian_cooper/archive/2008/03/04/some-recommended-books.aspx

Tue, 08 Apr 2008 15:25:18 GMT

Pingback from development.codebetter.com/.../some-recommended-books.aspx

Finds of the Week - April 6, 2008 » Chinh Do

Finds of the Week - April 6, 2008 » Chinh Do — Tue, 08 Apr 2008 03:26:24 GMT

Pingback from Finds of the Week - April 6, 2008 » Chinh Do