Question

I’ve done some searches (over the web and SO) but so far have been unable to find something that directly answer this:

Is there anyway to force L2S to use a Stored Procedure when acessing a Database?

This is different from simply using SPROC’s with L2S: The thing is, I’m relying on LINQ to lazy load elements by accessing then through the generated “Child Property”. If I use a SPROC to retrieve the elements of one table, map then to an entity in LINQ, and then access a child property, I believe that LINQ will retrieve the register from the DB using dynamic sql, which goes against my purpose.

---

UPDATE:

Sorry if the text above isn’t clear. What I really want is something that is like the “Default Methods” for Update, Insert and Delete, however, to Select. I want every access to be done through a SPROC, but I want to use Child Property.

Just so you don’t think I’m crazy, the thing is that my DAL is build using child properties and I was accessing the database through L2S using dynamic SQL, but last week the client has told me that all database access must be done through SPROCS.

Answer 1

i don’t believe that there is a switch or setting that out of the box and automagically would map to using t sprocs the way you are describing. But there is now reason why you couldn’t alter the generated DBML file to do what you want. If I had two related tables, a Catalog table and CatalogItem tables, the Linq2SQL generator will naturally give me a property of CatalogItems on Catalog, code like:

private EntitySet<shelf_myndr_Previews_CatalogItem> _shelf_myndr_Previews_CatalogItems;

[global::System.Data.Linq.Mapping.AssociationAttribute(Name="CatalogItem", Storage="_CatalogItems", ThisKey="Id", OtherKey="CatalogId")]
public EntitySet<CatalogItem> CatalogItems
    {
        get
        {
            return this._CatalogItems;
                            //replace this line with a sproc call that ultimately
                            //returns the expected type
        }
        set
        {
            this._CatalogItems.Assign(value);
                            //replace this line with a sproc call that ultimately
                            //does a save operation
        }
    }

There is nothing stopping you from changing that code to be sproc calls there. It’d be some effort for larger applications and I’d be sure that you be getting the benefit from it that you think you would.