Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. COI'm refering to the ORM designer and the insert/update/delete methods that you can use to specify which sp to run when SubmitChanges gets called. I think what you are saying is to basically do away with the SubmitChanges approach and write my own insert methods. Yes this is ok, but kind of defeats the purpose of using the ORM and means having to maintain my own methods instead of leaving it up to the auto-generator thingy. What I really hoped was that setting the insert method in the ORM on a sub-class would propergate up the heirachy, but it doesn't look like it does. Thanks though.
      singulars
    2. COThat's not what I meant, actually. The calling code with InsertOnSubmit and SubmitChanges would remain exactly the same. I am suggesting a new method in the Class1 entity to get around the limitation of the designer. It would still be fully encapsulated within the entities. I understand the frustration about it not just working the way you have it, though.
      singulars
    3. COSorry, I think I got my own wires crossed. I looked over your solution again and with once I understood exactly what you were getting at it suddenly clicked. So I didn't need to rely on the designer, just use the datacontext's partial class (didn't realise i could do that either). I'll add what I did to my post. Many thanks Bryan, saved me bacon as I'm pushing for us to be using LinqToSql and LinqToEntities in future.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload