Hi,
I have a problem when forcing another schema in version 1.0.2004.2.
The Oracle schema in production is not the same as the development one, so I force the schema in the app.config using :
<add key="SchemaNameUsageSetting" value="1"/>
<add key="SchemaNameToUse" value="MyProductionSchema" />
I works fine but when I want to save a new entity containing an Identity field, I get an error "Sequence not found" in my production environment.
When looking in the class PersistenceInfoFactory, it appears that the PersistenceInfoBucket is created with the schema hard-coded for the sequence.
For example :
private static PersistenceInfoBucket CreateENG_JOBPARAMSEntityBucket()
{
PersistenceInfoBucket toReturn = new PersistenceInfoBucket();
toReturn.AddFieldPersistenceInfo("PAR_OID", new FieldPersistenceInfo(@"PRCDSK", "ENG_JOBPARAMS", "PAR_OID", false, (int)OracleDbType.Decimal, 22, 0, 10, true, "PRCDSK.SEQ_ENG_PARAM"));
toReturn.AddFieldPersistenceInfo("JOB_OID", new FieldPersistenceInfo(@"PRCDSK", "ENG_JOBPARAMS", "JOB_OID", true, (int)OracleDbType.Decimal, 22, 0, 10, false, ""));
toReturn.AddFieldPersistenceInfo("PAR_NAME", new FieldPersistenceInfo(@"PRCDSK", "ENG_JOBPARAMS", "PAR_NAME", false, (int)OracleDbType.Varchar2, 50, 0, 0, false, ""));
toReturn.AddFieldPersistenceInfo("PAR_VALUE", new FieldPersistenceInfo(@"PRCDSK", "ENG_JOBPARAMS", "PAR_VALUE", false, (int)OracleDbType.Varchar2, 2000, 0, 0, false, ""));
return toReturn;
}
Is it a bug ?
In previous version, the schema was not hard-coded.
Is it possible to have a fix ?
Thanks a lot.