Hi,

LLBLGen 2.5 Final (April 23d, 2008 ) and Oracle 11g.

I have noticed that generated action procedure call code has the name of the db schema hardcoded. Does this mean that action procedures ignore the CatalogNameOverwriteHashtable hashtable and catalogue overwritting? Is there a way around this so that the action procedure calling also takes CatalogNameOverwriteHashtable into account?

Thanks

Regards, Dalibor

I have noticed that generated action procedure call code has the name of the db schema hardcoded

Do you mean the C# or VB.NET code, or the runtime SQL query? If you are using CatalogNameOverwrites, the generated SQL query at runtime should point to the new catalog name.

Hi, Sorry for not being more precize. Here is an example of the action procedure code generated by the desinger:

        /// <summary>
        /// Calls stored procedure 'SKLAD_ARTIKLI.APPROVE_STOCK_TRANSFER'. Can't have any cursors.<br/><br/>
        /// 
        /// </summary>
        /// <param name="pArtStockTransferId">Input parameter of stored procedure</param>
        /// <param name="pUserId">Input parameter of stored procedure</param>
        /// <param name="adapter">The DataAccessAdapter object to use for the call</param>
        /// <returns>Amount of rows affected, if the database / routine doesn't surpress rowcounting.</returns>
        public static int SkladArtikliApproveStockTransfer(System.Decimal pArtStockTransferId, System.Decimal pUserId, DataAccessAdapter adapter)
        {
            OracleParameter[] parameters = new OracleParameter[2];
            parameters[0] = new OracleParameter("P_ART_STOCK_TRANSFER_ID", OracleType.Number, 0, ParameterDirection.Input, true, 22, 0, "",  DataRowVersion.Current, ConvertNullToDBNull(pArtStockTransferId));
            parameters[1] = new OracleParameter("P_USER_ID", OracleType.Number, 0, ParameterDirection.Input, true, 22, 0, "",  DataRowVersion.Current, ConvertNullToDBNull(pUserId));
            int toReturn = adapter.CallActionStoredProcedure("DEV.SKLAD_ARTIKLI.APPROVE_STOCK_TRANSFER", parameters);

            return toReturn;
        }
    

As you can see the catalog name 'DEV' is located inside the generated code. Since I do not see any output from calling action procedures in the trace I can not say if the catalog overrides works for them or not. I just assumed that they do not since the catalog name looks like a part of the procedure name.

StoredProcedures indeed takes into account CatalogNameOverwrites. If you follow the method adapter._CallActionStoredProcedure _you will see that there is another method called _CreateCorrectStoredProcedureName _which creates the correct name of the stored procedure.

So it should work, please do some test (you could debug your Code to get into that methods and see what name is actually used). If you still have troubles with the overriding please post the LLBLGenPro version and RuntimeLibraries version.

Hope helful

Hi,

Thank you for the reply. We will test it.

Regards, Dalibor