As it turnes out it wasn't at all that dificcult. In the IDataSourceKeyResolver implementation, where I create the ClientEdmKey with correct user credentials, I also change the SSDL reference in the connection string. I grab the original single SSDL file built with the project, creates a copy, replaces the schema name in the copy, and finally inserts a reference to the copy in the connection string.

 

With this solution we can dynamically add new customers and schemas to the database, update a single configuration file, and the application will automatically adapt to the new schema at logon time. We don't have to manually maintain and update multiple SSDL files.

 

Mikael

 

 

 

Yes, this is a consequence of the inner working of EF.

 

For SQL Server there is no problem with having the schema name constant, since you have the concept of catalogs to manage different databases within one single server instance. With Oracle there is only one database for a single server instance, and hence we need to vary the schema name to select which data to work with.

 

If I understand correctly this is not directly related to DF, but actually a consequence of the inner working of EF. I'll follow it up with Microsoft/Oracle regarding EF instead, and post any findings here later.

 

Thanks anyway,

Mikael

 

 

Different schema names is a pretty bad idea with an ORM unless you don't mind maintaining multiple mappings.

In production another database server will be used, as well as different schema names (we have one separate schema for each customer). All schemas of course have identical table definitions.

 

I have succesfully created an implementation of IDataSourceKeyResolver that returns a ClientEdmKey with the approriate connection string to switch between development and production servers, as well as log in with different credentials. What I am NOT able to do is to select the correct schema. Every query I make tries to address the dev schema which the model initially was created from. I can see that this schema name is stored in the edmx file for each table.

 

How can I dynamically change the schema at run time like I can change server and credentials?

 

Mikael