Comments on: Entity Framework Stored Procedure Generation

By: PeterDer

PeterDer — Thu, 21 Aug 2008 05:14:42 +0000

Where did you got that nice syntax coloring from???

By: David DeWinter

David DeWinter — Mon, 28 Jul 2008 19:10:25 +0000

Hello Vitaly,

Thank you for your comments. I re-read the code and noticed that it is not updating any identity columns as you describe.

Can you post the CREATE TABLE script of the table for which the SPs would break?

Thanks!

David

By: Vitaly A. Shulgin

Vitaly A. Shulgin — Thu, 17 Jul 2008 08:41:10 +0000

Thank you for article and T4 template.
I have tested it and found incorrect behaviour on table with IDENTITY column. It generates UPDATE SP wich allow to change value of that column, even it’s not possible at SQL-server level. Attemp to call such SP will results to SQL error. Is there something I’ve missed?

By: Emir Treviño

Emir Treviño — Fri, 04 Jul 2008 20:26:59 +0000

please, check my realese about code generation with T4 template from Entity Framework model,

http://www.codeplex.com/sfs

By: Ariful Ambia Noman

Ariful Ambia Noman — Thu, 03 Jul 2008 10:40:19 +0000

very helpfully article. i like it

By: Function Mapping with Inherited Types « Ryan Hauert

Function Mapping with Inherited Types « Ryan Hauert — Tue, 20 May 2008 20:07:21 +0000

[...] map the entities in the hierarchy to the same three stored procedures, which I generated using the T4 template David DeWinter and I developed. The Insert, Update, and Delete stored procedures are defined [...]

By: GarethJ's WebLog : A rash of bloggers

GarethJ's WebLog : A rash of bloggers — Wed, 14 May 2008 04:35:02 +0000

[...] article on using T4 to generate a complete set of sProcs for the new ADO.Net Entity Framework. It appears that he co-conspired on it with Ryan [...]

By: Stéphane

Stéphane — Fri, 02 May 2008 09:14:55 +0000

Working… So NEVER do an insert without a result binding :D, that just doesn’t work! (at least not more than 1 time)

By: Stéphane

Stéphane — Fri, 02 May 2008 07:59:25 +0000

Hi David,

Actually, I think my problem is coming exactly from what you just explained. When I’m inserting a new row, it works the 1st time, on the next insertion, it tells me that there is a conflict, that an object with the same key already exists in the ObjectContext. I knew it could return a value generated by the database, but I didnt know it would populate the object in the ObjectContext!
So appartently, it’s mandatory to design the stored procedure that return the key value of the inserted object I go try this right now to confirm!

Thank you !!

By: David DeWinter

David DeWinter — Thu, 01 May 2008 23:40:52 +0000

The reason the insert stored procedure selects information after the insert occurs is to retrieve values that the database generates (e.g. identity columns, computed columns) for use in the application. The stored procedure doesn’t return an EntityObject; instead it utilizes the ResultBinding element (search for ResultBinding on the linked page) to map some values to properties in the EntityObject I insert.

Here’s an example:

Here, when I insert StyleAttribute into the database, the database generates the StyleAttributeId. When it comes back into my code, StyleAttributeId is populated with what the database generated.

As for your troubles with your stored procedures, you are free to email me at david —dot— dewinter —at— rev-net —dot— com. I’ll get back to you as soon as I can.