Using Stored Procedures for Change Processing in the ADO.NET Entity Framework

Using Stored Procedures with ADO.Net Entity Framework

Guy Burstein's Blog — Fri, 09 Mar 2007 12:46:00 GMT

Last October, when I gave a talk about ADO.Net Entity Framework , one missing piece was to enable updating

re: Using Stored Procedures for Change Processing in the ADO.NET Entity Framework

Chris Moore — Sun, 11 Mar 2007 23:47:20 GMT

Ok, this is a little off-topic for this post, but an important issue that is not addressed anywhere that I can find:

The ADO Entity Framework seems to take us a certain part of the way, but not all the way, to what Fowler calls "Persistance Ignorance". That is, ideally, one would like to be able to establish a domain layer that contained entities that are in no way aware of the underlying persistence mechanism being used. This would allow one to easily replacing the actual data access layer without being concerned about this affecting the domain layer.

With the ADO.Net Entity Framewok I see two main violations of this principal that, as far as I can tell, cannot be circumvented:

1. Entities must subclass the Entity framework class, and

2. It is necessary to attach various attributes to entity properties.

I can live with (1); with the appropriate discipline, one can avoid any dependency on the parent class from within the domain layer. If later I decide to use another persistence mechanism than ADO, I can easily remove Entity from the inheritance tree.

Item (2), on the other hand, is much more troublesome and I can't see why attaching these attributes is strictly necessary. Notwithstanding the Data Contract attributes, all of the information encapsulated by these attached attributes is derived from information contained in the CSDL file - which is available at runtime via the metadata workspace.

These considerations lead to the following questions:

1. Why is it necessary to have CSDL redundant metadata; why can't the single source of this information just be the CSDL specification itself?

2. Was the concept of "persistence ignorance" considered when the framwork was being designed? If so, why weren't the tenets of this principal followed more closely?

3. Am I missing something? Is there some construct that would allow complete (or even allow one to come closer to) PI? Is there any way I could create a domain class that has no dependency at all on the entity framework and yet still have persistence services be managed by the framwork provided the CSDL, MSL and SSDL are specified?

I think what you guys are doing here is really cool, interesting and useful; I just wish your approach allowed complete independence of one's domain layer from persistence infrastructure

re: Using Stored Procedures for Change Processing in the ADO.NET Entity Framework

Jacky Lee — Wed, 21 Mar 2007 02:39:42 GMT

I just worry about the performance and security of dynamic SQL, which is widely adopted as the primary tool instead of stored procedure when referring to LINQ and other similar techs. So I insist that I still use LINQ to invoke stored procedures rather than to generate a dynamic SQL statement. I just hope that the LINQ team can make BETTER support for stored procedures.~~~~~

re: Using Stored Procedures for Change Processing in the ADO.NET Entity Framework

Tim McCarthy — Mon, 26 Mar 2007 00:37:11 GMT

I made a simpler example with just one table called Customer. Every time I try this I get the following error:

System.Data.MappingException was unhandled

Message="A mapping function binding specifies an unknown function CustomerInsert. File URI: file:///C:/Documents and Settings/Administrator/My Documents/Visual Studio Codename Orcas/Projects/EntityFrameworkSamples/EntityDriver/bin/Debug/Model1.msl. Line Info: 12, 10."

Source="System.Data.Entity"

StackTrace:

at System.Data.Mapping.StorageMappingItemLoader.FunctionMappingLoader.LoadAndValidateFunctionMetadata(XPathNavigator nav)

at System.Data.Mapping.StorageMappingItemLoader.FunctionMappingLoader.LoadEntityTypeFunctionMapping(XPathNavigator nav, Boolean allowCurrentVersion, Boolean allowOriginalVersion, EntityType entityType)

at System.Data.Mapping.StorageMappingItemLoader.LoadEntityTypeFunctionMapping(XPathNavigator nav, StorageEntitySetMapping entitySetMapping, StorageEntityTypeMapping entityTypeMapping)

at System.Data.Mapping.StorageMappingItemLoader.LoadEntityTypeMapping(XPathNavigator nav, StorageEntitySetMapping entitySetMapping, String tableName, EntityContainer storageEntityContainerType)

at System.Data.Mapping.StorageMappingItemLoader.LoadEntitySetMapping(XPathNavigator nav, StorageEntityContainerMapping entityContainerMapping, EntityContainer storageEntityContainerType)

at System.Data.Mapping.StorageMappingItemLoader.LoadEntityContainerMapping(XPathNavigator nav, StorageEntityContainerMapping entityContinerMapping, EntityContainer storageEntityContainerType)

at System.Data.Mapping.StorageMappingItemLoader.LoadMappingChildNodes(XPathNavigator nav, Boolean shouldDefaultUnspecifiedMaps)

at System.Data.Mapping.StorageMappingItemLoader.LoadMappingItems(XPathNavigator nav)

at System.Data.Mapping.StorageMappingItemLoader.LoadMappingItems()

at System.Data.Mapping.StorageMappingItemCollection.LoadItems(IEnumerable`1 filePaths)

at System.Data.Mapping.StorageMappingItemCollection..ctor(EdmItemCollection edmCollection, IEnumerable`1 filePaths)

at System.Data.EntityClient.EntityConnection.CreateMetadataWorkspace(DbConnectionOptions connectionOptions, DbConnection connection)

at System.Data.EntityClient.EntityConnection.ChangeConnectionString(String newConnectionString)

at System.Data.EntityClient.EntityConnection..ctor(String connectionString)

at System.Data.Objects.ObjectContext.CreateEntityConnection(String connectionString, String defaultContainerName)

at System.Data.Objects.ObjectContext..ctor(String connectionString, String defaultContainerName)

at EntityDriver.Program.ShowCustomers() in C:\Documents and Settings\Administrator\My Documents\Visual Studio Codename Orcas\Projects\EntityFrameworkSamples\EntityDriver\Program.cs:line 30

at EntityDriver.Program.Main(String[] args) in C:\Documents and Settings\Administrator\My Documents\Visual Studio Codename Orcas\Projects\EntityFrameworkSamples\EntityDriver\Program.cs:line 20

at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)

at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)

at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart()

I have defined the CustomerInsert function properly in my .msl and .ssdl files, but it still will not work.

Can you post your actual code files for this example?

ADO.Net Entity Framework Stored Procedures

Guy Burstein's Blog — Wed, 25 Jul 2007 02:22:08 GMT

ADO.Net Entity Framework Stored Procedures Last October, when I gave a talk about ADO.Net Entity Framework

Entity Framework - Object Services Level. CUD with Stored Procedures.

Mike Taulty's Blog — Wed, 29 Aug 2007 01:33:28 GMT

How would you get the Entity Framework to map inserts, updates, deletes through a stored procedure layer...

re: Using Stored Procedures for Change Processing in the ADO.NET Entity Framework

dat — Wed, 26 Sep 2007 23:42:40 GMT

This approach is so complicated. I would never want to edit the xml. Why dont you have a tool to do that? I see LINQ To SQL have a desnger surface to drag and drop sp from Server Explorer.

Entity Framework FAQ

system.data.objects dev guy — Thu, 15 Nov 2007 00:56:37 GMT

Entity Framework FAQ Version 0.2 – 11/14/2007 New in this version of the FAQ… · Table of contents with

re: Using Stored Procedures for Change Processing in the ADO.NET Entity Framework

ASN — Fri, 23 Nov 2007 07:09:25 GMT

to Tim

<cs:FunctionName="dbo.CreateProduct">

<cs:FunctionName="ProductInventory.Store.CreateProduct">

re: Using Stored Procedures for Change Processing in the ADO.NET Entity Framework

ASN — Fri, 23 Nov 2007 07:09:31 GMT

to Tim

<cs:FunctionName="dbo.CreateProduct">

<cs:FunctionName="ProductInventory.Store.CreateProduct">

ADO.NET team blog : Using Stored Procedures for Change Processing in the ADO.NET Entity Framework

Dating — Sun, 01 Jun 2008 05:49:11 GMT

Most people who’ve played with the ADO.NET Entity Framework eventually ask whether they can replace the SQL statements it generates with stored procedures of their own. This is important in many applications because direct table access is not allowed

ADO.NET team blog : Using Stored Procedures for Change Processing in the ADO.NET Entity Framework

Weddings — Fri, 06 Jun 2008 06:54:15 GMT

Entity Framework FAQ(转)

江南白衣 — Wed, 11 Jun 2008 19:18:45 GMT

The Entity Framework enables developers to reason about and write queries in terms of the EDM model rather than the logical schema of tables, joins, foreign keys, and so on. Many enterprise systems have multiple applications/databases with varying degrees

Entity Services, Metadata & Mapping

system.data.objects dev guy — Sun, 10 Aug 2008 11:27:56 GMT

Part of the Entity Framework FAQ . 13. EDM 13.1. Does Entity Framework support Abstract types in EDM

re: Using Stored Procedures for Change Processing in the ADO.NET Entity Framework

Varun — Fri, 28 Nov 2008 21:00:10 GMT

Has anyone done the mapping of an oracle stored procedure for insert and mapped the resultbinding columns to get the ID back for the insert, I am ending up with an error that this field is not avaliable in the datareader. If anyone has successfully done this please could you post the insert stored procedure.

Thanks a lot in advance