Page 1 of 1
How to use new workaround for IgnoreSchemaName
Posted: Thu 05 May 2011 15:40
by quip85673456
I have the beta for 6.30.145, but I can't figure out how to use the new IgnoreSchemaName workaround.
Can you explain how to set that property, is it in code, or in the model, or something else?
Update: Nevermind, this appears to work:
Code: Select all
var config = Devart.Data.Oracle.Entity.Configuration.OracleEntityProviderConfig.Instance;
config.Workarounds.IgnoreSchemaName = true;
Posted: Fri 06 May 2011 06:34
by Shalex
Posted: Tue 10 May 2011 08:55
by syl74
Hello,
I'm using dotConnect for Oracle 610.141 with the Entity Framework support (no Entity Developer).
Because my tables structures can be deployed on 2 differents schema, I have to remove the schema name in the EntitySet info in the SSDL. If the tag store:Schema= is not present, then my model works on both schemas.
The problem is when I update my model from the database. All tables are displayed as *new* and *todelete* because the designer cannot make the "join" between tables already declared in the model and tables present in the database (because of the store:Schema info missing in the SSDL)
Question : is the new "IgnoreShemaName" can help me in this situation ?
Is there a way to activate this workaround in the config file used by entity framework when updating a model from database ?
Thanks for your help.
Posted: Tue 10 May 2011 09:06
by syl74
I've found the solution my self.
1- Do not remove the store:Schema info in the SSDL
2- Add the following code in my service constructor
var config = Devart.Data.Oracle.Entity.Configuration.OracleEntityProviderConfig.Instance; config.Workarounds.IgnoreSchemaName = true;
It works !
PS : good job also for the fix for "StoreGeneratedPattern".