LLBLGEN 3.1 Release date:17-Jun-2011 .NET Framework 2.0 Oracle 9i/10g (MSORACLE)

I have two schema's one BCLUB1868 and another DEMOERP.

I was using BCLUB1868 during initial stage of development. Now I would like to use DEMOERP.

I was able to successfully use schema name overwrite by referencing the manual.

But Stored Proc used in BCLUB1868 is not working with DEMOERP even if schema name overwrite is used. However views are working fine in DEMOERP.

What do you mean by is not working? Is the wrong schema name been used, or SPs are not reachable?

Walaa wrote:

What do you mean by is not working? Is the wrong schema name been used, or SPs are not reachable?

Means It is refering to SP in BCLUB1868 and NOT DEMOERP. Definitely schema name is not wrong since views and entities are working correctly. Problem is only referring to SP's.

I think because LLBLGEN generates like this "\"BCLUB1868\".\"SP_ROOMRESERVATIONREPORT\"", "SPRoomreservationreport")?

In this case, will schema overwrite in config will work ?

In this case, will schema overwrite in config will work ?

It should work.

How exactly are you overwriting the schema, when calling a sp?

Walaa wrote:

In this case, will schema overwrite in config will work ?

It should work.

How exactly are you overwriting the schema, when calling a sp?

when calling SP?

I have only done this in .config file what am i supposed to do while calling SP?

<configSections> <section name="oracleSchemaNameOverwrites" type="System.Configuration.NameValueSectionHandler" /> </configSections>

<oracleSchemaNameOverwrites> <add key="BCLUB1868" value="DEMOERP" /> </oracleSchemaNameOverwrites>

Which config file?

Walaa wrote:

Which config file?

app.config of my startup project which loads the forms

Yeah I know, which one, I mean inside which project?

Walaa wrote:

Yeah I know, which one, I mean inside which project?

I have only one app.config ! which is in my startup project

You mean to say i need to add this in DBSpecific project also ?

No, this should be added in the config file used by your application.

Some people make the mistake to add these tags in the generated config file, not in the executable application's config file.

Walaa wrote:

No, this should be added in the config file used by your application.

Some people make the mistake to add these tags in the generated config file, not in the executable application's config file.

It is in my executable app.config

Ok so other questions are.

1- Whe you say:

I was able to successfully use schema name overwrite by referencing the manual.

So you mean you have used the same configuration file, and you could correctly fetch entities from the required schema.

2- Could you be making some XML tagging mistake as in here: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=16439

Walaa wrote:

Ok so other questions are.

1- Whe you say:

I was able to successfully use schema name overwrite by referencing the manual.

So you mean you have used the same configuration file, and you could correctly fetch entities from the required schema.

2- Could you be making some XML tagging mistake as in here: http://www.llblgen.com/tinyforum/Messages.aspx?ThreadID=16439

Yes I have used same config file and could correctly fetch entities from the required schema. There is no other app.config present in any projects. I do not see any XML tag errors.

I have attached config file

This should work for procs too. We'll look into it.

Otis wrote:

This should work for procs too. We'll look into it.

But not working Otis. Will await your response

It's a bug, the name of the target table schema is stored without "" and therefore it goes OK for entity fetches, but the stored proc name has the schema wrapped in "", and there it goes wrong. It works for per-call schema overwrites (the one you can set with an object on the adapter) but not for overwrites defined in the config file (which are global) as it doesn't strip the "" from the schema name of the proc.

Workaround is:

<oracleSchemaNameOverwrites>
    <add key="BCLUB1868" value="DEMOERP" />
    <add key='"BCLUB1868"' value="DEMOERP" />
</oracleSchemaNameOverwrites>

We're working on a fix, I'll attach a fixed Oracle DQE when we're done.

See attached DQE for the fix.

Otis wrote:

See attached DQE for the fix.

Work around works fine but attached DQE fix behave the same as it was earlier. I mean SP does not work.

shekar wrote:

Otis wrote:

See attached DQE for the fix.

Work around works fine but attached DQE fix behave the same as it was earlier. I mean SP does not work.

Are you sure you use the new DQE dll? (please check whether you have the DQE in the GAC. If so, remove it). If you copied the dll into the llblgen pro installation folder, make sure you do that as administrator.

The DLL has as file version 3.1.11.630, so right-click on the dll in windows explorer -> properties -> version tab. This should reveal the above number, not 3.1.11.207. Check this in the bin folder of your application, so the dll that's used at runtime is the right one.

Otis wrote:

shekar wrote:

Otis wrote:

See attached DQE for the fix.

Work around works fine but attached DQE fix behave the same as it was earlier. I mean SP does not work.

Are you sure you use the new DQE dll? (please check whether you have the DQE in the GAC. If so, remove it). If you copied the dll into the llblgen pro installation folder, make sure you do that as administrator.

The DLL has as file version 3.1.11.630, so right-click on the dll in windows explorer -> properties -> version tab. This should reveal the above number, not 3.1.11.207. Check this in the bin folder of your application, so the dll that's used at runtime is the right one.

I do not use GAC. Version name is 3.1.11.630 which was copied to LLBLGEN installation folder. Yes I am the administrator of the PC. Even the app bin folder DLL version is 3.1.11.630

You're right!

What happened was this: - I created a test project on SCOTT - Altered the 'SCOTT' schema to be 'HR' in the procs - worked with the code, fixed it - Wondered why it didn't occur for entities - Added an entity, regenerated the code, but forgot (!) to change SCOTT into HR again - tests passed (of course).

Will re-investigate. Sorry for this inconvenience!

Well... I re-tested it, but it still works properly:

procs:

/// <summary>Creates the call object for the call 'Getdeptno' to stored procedure 'PR_GETDEPTNO'.</summary>
/// <param name="dataAccessProvider">The data access provider.</param>
/// <param name="pEmpno">Input parameter</param>
/// <param name="oDeptno">Output parameter</param>
/// <returns>Ready to use StoredProcedureCall object</returns>
private static StoredProcedureCall CreateGetdeptnoCall(IDataAccessCore dataAccessProvider, System.Decimal pEmpno, System.Decimal oDeptno)
{
    return new StoredProcedureCall(dataAccessProvider, "\"HR\".\"PR_GETDEPTNO\"", "Getdeptno")
                    .AddParameter("P_EMPNO", "Number", 0, ParameterDirection.Input, true, 38, 38, pEmpno)
                    .AddParameter("O_DEPTNO", "Number", 0, ParameterDirection.Output, true, 38, 38, oDeptno);
}

/// <summary>Creates the call object for the call 'PackageATestfunc' to stored procedure 'PackageA.TESTFUNC'.</summary>
/// <param name="dataAccessProvider">The data access provider.</param>
/// <param name="returnValue">ReturnValue parameter</param>
/// <param name="aparam">Input parameter</param>
/// <returns>Ready to use StoredProcedureCall object</returns>
private static StoredProcedureCall CreatePackageATestfuncCall(IDataAccessCore dataAccessProvider, System.String aparam, System.String returnValue)
{
    return new StoredProcedureCall(dataAccessProvider, "\"HR\".\"PackageA.TESTFUNC\"", "PackageATestfunc")
                    .AddParameter("RETURN_VALUE", "VarChar", 4000, ParameterDirection.ReturnValue, true, 0, 0, returnValue)
                    .AddParameter("APARAM", "VarChar", 4000, ParameterDirection.Input, true, 0, 0, aparam);
}

don't exist in HR, but in scott.

<oracleSchemaNameOverwrites>
    <add key="HR" value="SCOTT"/>
</oracleSchemaNameOverwrites>

commenting that out fails the code, having the overwriting works.

code:

string retVal = string.Empty;
ActionProcedures.PackageATestfunc("foo", ref retVal);

decimal deptno=0.0M;
ActionProcedures.Getdeptno(1.0M, ref deptno);

Succeeds..... They're properly executed on SCOTT. I verified it twice, also with the debugger...

I've attached the exact dll I'm using (which is a debug build).

Otis wrote:

Well... I re-tested it, but it still works properly:

procs:

/// <summary>Creates the call object for the call 'Getdeptno' to stored procedure 'PR_GETDEPTNO'.</summary>
/// <param name="dataAccessProvider">The data access provider.</param>
/// <param name="pEmpno">Input parameter</param>
/// <param name="oDeptno">Output parameter</param>
/// <returns>Ready to use StoredProcedureCall object</returns>
private static StoredProcedureCall CreateGetdeptnoCall(IDataAccessCore dataAccessProvider, System.Decimal pEmpno, System.Decimal oDeptno)
{
    return new StoredProcedureCall(dataAccessProvider, "\"HR\".\"PR_GETDEPTNO\"", "Getdeptno")
                    .AddParameter("P_EMPNO", "Number", 0, ParameterDirection.Input, true, 38, 38, pEmpno)
                    .AddParameter("O_DEPTNO", "Number", 0, ParameterDirection.Output, true, 38, 38, oDeptno);
}

/// <summary>Creates the call object for the call 'PackageATestfunc' to stored procedure 'PackageA.TESTFUNC'.</summary>
/// <param name="dataAccessProvider">The data access provider.</param>
/// <param name="returnValue">ReturnValue parameter</param>
/// <param name="aparam">Input parameter</param>
/// <returns>Ready to use StoredProcedureCall object</returns>
private static StoredProcedureCall CreatePackageATestfuncCall(IDataAccessCore dataAccessProvider, System.String aparam, System.String returnValue)
{
    return new StoredProcedureCall(dataAccessProvider, "\"HR\".\"PackageA.TESTFUNC\"", "PackageATestfunc")
                    .AddParameter("RETURN_VALUE", "VarChar", 4000, ParameterDirection.ReturnValue, true, 0, 0, returnValue)
                    .AddParameter("APARAM", "VarChar", 4000, ParameterDirection.Input, true, 0, 0, aparam);
}

don't exist in HR, but in scott.

<oracleSchemaNameOverwrites>
    <add key="HR" value="SCOTT"/>
</oracleSchemaNameOverwrites>

commenting that out fails the code, having the overwriting works.

code:

string retVal = string.Empty;
ActionProcedures.PackageATestfunc("foo", ref retVal);

decimal deptno=0.0M;
ActionProcedures.Getdeptno(1.0M, ref deptno);

Succeeds..... They're properly executed on SCOTT. I verified it twice, also with the debugger...

I've attached the exact dll I'm using (which is a debug build).

This dll works fine otis. Thanks for all your help