I think you are right. I had hoped for more commonality among LINQ implementation than just IQueryable. What is the point of an OR mapper if it can only map to a single DBMS family? Yes, I know, LINQ to SQL is a very easy and fast way for common scenarios on SQL Server. I just had hoped for something in its architecture that would help me access other DBMS as well.
Will you take up this topic in your new book, the (lack of) commonality among LINQ implemenations and what to do about it?
Should I look to LINQ to Entities instead?
Thanks,
Brian
/brian