Changing the underlying schema name without recompilation

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Post Reply
rsnell72
Posts: 4
Joined: Thu 01 Oct 2009 20:40

Changing the underlying schema name without recompilation

Post by rsnell72 » Thu 01 Oct 2009 20:41

I am using dotConnect for Oracle 5.25.44 to connect to an Oracle 10g instance. I am using the EDM Wizard to generate a conceptual model of the database which is then used by ADO.NET Data Services to expose a RESTful web service. I cannot dictate to the customer what the schema owner will be named in their production environment. I also can not install visual studio on their production network and recompile to a new connection and schema.

Now, the connection string is a configuration element in the web.config file, but the Schema name appears to be embedded in the ssdl file generated as part of the compilation. How do I make this a configuration parameter and recompile for production use?

AndreyR
Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Fri 02 Oct 2009 10:10

I suggest you to remove the Schema attribute from EntityContainers and all schema names from the
DefiningQuery elements (if there are any) in your .ssdl file using an XML editor.
In this case the problem with different schema names will be solved.

rsnell72
Posts: 4
Joined: Thu 01 Oct 2009 20:40

Post by rsnell72 » Fri 02 Oct 2009 13:06

Thank you very much. That worked splendidly.

Post Reply