Linq stored procedure update

Then I use PersonType to discriminate. When I try to customize the Insert method used to insert an Employee I can do it, however only the EmployeeNumber property is available to map. I need to get this to work! I tried creating a partial class for my DataContext and adding something like this:.

Code Block public void InsertEmployee Employee object. Parameters here However LINQ does not appear to call this function? In your example, the base class is Person, so you'd need to define InsertPerson and then multiple method representing stored procedures.

Learn more. Asked 12 years, 8 months ago. Active 12 years, 8 months ago. Viewed 2k times. Improve this question. Jalpesh Vadgama Jalpesh Vadgama Add a comment.

Active Oldest Votes. Improve this answer. Serapth Serapth 6, 3 3 gold badges 28 28 silver badges 38 38 bronze badges. If you have only one or two tables that fall into this bucket that might be the best approach to use. I could have used the VB Labmda equivalent instead which you have above , but I've found a lot of VB developers are still new to that syntax, and so doing it via the query syntax feels a little more understandable.

They ultimately execute the same logic at runtime - so either works. Hi Roger, I'll go into more detail on lazy vs. Here are a few comments, though, that I posted in response to one of David's posts: In cases where the relationship between two entities is n:1 , LINQ to SQL does a JOIN as opposed to separate queries since these tend to be safe from a data explosion perspective.

Category ; options. OrderDetails ; options. Order ; db. ToList ; You'd find that only 1 query is executed against the SQL database for everything even though you are bringing back all of the Products and their associated Category and OrderDetail information. Hi egergo, Can you send me email scottgu microsoft. Thanks, Scott. Hey Scott, I hope you'll consider making a post about how to create a good BLL with Linq - or if you have a good place to read?

Im new at. Linq seems like a very interesting technology, but it would be nice to know that im doing it correct all the way ;.

Is there any way to execute the business rules as you've defined them above without actually doing the update? There are some occasions where I'd like to validate the data first without doing an actual update yet. NET This sounds like a scenerio that I will encounter in this move as there are about 5 or 6 places that the app does a M:M join. Can you please post whatever you find out here for us all to view.

Thanks in Advance, Steve. My test DB, Code and Result can be downloaded from here. Hi Scott, thanks for these articles, its a real help while I'm learning this new tech. Question that might have already been asked: Can I somehow construct and map an enum to a lookup table in my database? So, instead of creating a class from the table, have it inspect the table contents at design time and create an enum.

You mention that optomistic concurrency is automatically handled. However, when using Stored Procs, this is not the case unless you are leveraging a Timestamp column. Since the OnTUpdate and OnTDelete no longer reference the originalValue, we can't pass this ourselves to the proc to manage our own concurrency.

That option existed in the beta1 implementation admittedly, it was mapped backwards at that time. When you add the propertychanging partial methods, these will execute everytime you set a property on them so no need to submit. I need to investigate some more to see whether there is a way to externally trigger that you could ceretainly add your own helper method to call it though. I'll cover this in my upcoming optimistic concurrency post.

For example lets say I have a proc that returns active orders for a specific sales account. You can use this to handle scenarios where you return multiple results. Hope this helps, Scott I'll cover this in my upcoming blog post on LoadOptions and. Right now the LINQ to SQL designer doesn't automatically support this - but you could in theory run your own tool to auto-generate an enum for this. I'd recommend being careful, though, since database cotents can change and you might find youself burning in stale data to enums if you aren't careful.

Thanks for all the great information. Your blog is my first stop for good ASP. NET tutorials. Thanks for the reply scott - I agree generated enums are probably not a smart architecture idea. Or should one just go out to third party tools like MyGeneration for this sort of thing? Thanks again Dave. Scott, Another great post! I have a 'slightly' unrelated question though - how similar will the Entity Framework be? Thanks, Jason. Hi Scott, Thanks for the answer. Yes you gave me the answer I was looking for.

Good day, Just one simple question - do you know any good MSSQL blog with tutorials of the same quality as yours? Are there anyway to query an entity without using lambda expression in C? Example: - Instead: db. Products where p. ProductID equals 1 select single p;. I try to build the examples and follow along. Is this page helpful? Please rate your experience Yes No. Any additional feedback? In this article.