deploy system into production environment

Discussion of open issues, suggestions and bugs regarding Entity Framework support in ADO.NET Data providers
Post Reply
Posts: 1
Joined: Fri 30 Jun 2017 09:18

deploy system into production environment

Post by huangzhtao » Fri 30 Jun 2017 09:23

I'm using Entity Framework with Oracle. When I want to deploy system into production environment(oracle schema name is different from development environment, tables names are the same), I meet a problem, the oracle schema name is written in the configure file. I'm using db-first mode.
How to make the schema configuration adapt to different environments?

Site Admin
Posts: 8247
Joined: Thu 14 Aug 2008 12:44

Re: deploy system into production environment

Post by Shalex » Mon 03 Jul 2017 09:03

It's more likely that there are the Schema attributes in the storage part of your model which are targeting specific schema (you can check this via dbMonitor). If so, remove the Schema="xxx" attributes from your SSDL. This can be done in design time of Entity Developer.

As an alternative, it is possible to leave the schema name in *.edml file, but turn off the generation of the schema name in run-time queries using the IgnoreSchemaName option of EF-provider configuration: ... tions.html.

Post Reply