I am using OpenAccess version 2011.2.713.3, Oracle 11g
When I populate the SP in rlinq, I found that the SP parameters are wrongly placed.
It is different from the actual SP parameters order.
The parameters appear in rlinq is like descending. (What is the idea?)
Result in data mismatch error occurred.
Reply me if the fix is done.
4 Answers, 1 is accepted
Can you please be a bit more descriptive on where exactly the problem occurs? Where do you see the mismatch? Basically the order of the parameters in your clr function should not have any effect of the execution of the stored procedure. Any further information you can provide us with will be of great help.Greetings,Petar
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>
This is my sp in oracle.
create or replace PROCEDURE My_SP
After I populate the SP in rlinq, here I use Update from Database method, and then try to call, the parameters are shown in descending order like:
Context cntx = new Context();
cntx.My_SP(Spara, Gpara, Apara);
And when I call the SP, data mismatch error is occurred.
I believe you can reproduce this issue very easily. The link below is the same issue face by other
Firstly I want to apologize for the inconvenience caused. We will investigate the wrong behavior on our side and will fix it the cause for this issue.
Actually you could use the new Low Level (ADO) API for Fetching Data Efficiently introduced in the latest release of the product. Helpful information how to execute stored procedures using the API can be found in the following help article and blog posts:
- “How to: Execute Stored Procedures”;
- “Telerik OpenAccess ORM - Stored procedure execution made easier”;
- “Telerik OpenAccess ORM - Executing an Oracle stored procedure that returns result sets”;
- “Telerik OpenAccess ORM - Execute stored procedures with out parameters, return values and multiple result sets”;
Hope that helps. If any other questions arise, do not hesitate to contact us back.
the Telerik team
Thanks for sharing the links. Very useful.
Hope high level API will be fixed soon as I prefer calling it like a C# function with parameters.