Oracle Schema needs to be in Config

skingaby · Post by **skingaby** » Mon 01 Jun 2009 22:54

Can you figure out a way to move the Oracle Schema name out of the EDML file and into the App.Config. We have 4 different schema names for Dev, Test, Maint and Prod. The way the Entity Developer works now, it looks like I will have to do a find and replace in the XML source before I promote to testing? Thanks, Simon

AndreyR · Post by **AndreyR** » Tue 02 Jun 2009 07:34

This option will be available in the upcoming build of Entity Developer.
It was already discussed here:
http://devart.com/forums/viewtopic.php?t=14974

skingaby · Post by **skingaby** » Thu 04 Jun 2009 02:39

The Post you referenced in your link is about the connection string, which the MS Entity Framework supports and you will support in the next version.

I am referring to the database Schema property, which is shown here:

That schema name "GCSD9" changes to GCSQ9 for QA, GCSM9 for Staging and GCSP9 for Production. That setting needs to be pulled out of the app.config file if at all possible.
Thanks,
Simon

AndreyR · Post by **AndreyR** » Thu 04 Jun 2009 14:14

I suppose this problem will be solved after the bug with config files we have discussed is fixed.
You will be able to have 4 different connection strings and to create the ObjectContext with the proper one.

Devart Forums

Oracle Schema needs to be in Config

Oracle Schema needs to be in Config

Not the Connection String, the Schema