This is a migrated thread and some comments may be shown as answers.
Stored Procedure
4 Answers 56 Views
This is a migrated thread and some comments may be shown as answers.
This question is locked. New answers and comments are not allowed.
Dave
Top achievements
Rank 1
Dave asked on 05 Aug 2011, 01:34 AM
Hi Telerik Team,

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.

Thanks.

4 Answers, 1 is accepted

Sort by
0
PetarP
Telerik team
answered on 10 Aug 2011, 02:03 PM
Hello Dave,

 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 >>

0
Dave
Top achievements
Rank 1
answered on 21 Aug 2011, 06:39 PM
Hi Telerik Team,

This is my sp in oracle.
create or replace PROCEDURE My_SP
(
  Apara VARCHAR2, 
  Spara NUMBER, 
  Gpara DATE

)
as
begin
.....
end;

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
http://www.telerik.com/community/forums/orm/databases/oracle-stored-procedures.aspx


Regards,
Dave
0
Damyan Bogoev
Telerik team
answered on 24 Aug 2011, 09:07 AM
Hi Dave,

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.

Regards,
Damyan Bogoev
the Telerik team

Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward! We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>

0
Dave
Top achievements
Rank 1
answered on 26 Aug 2011, 10:11 AM
Hi Damyan Bogoev,

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.

Cheers,
Dave
Tags
Development (API, general questions)
Asked by
Dave
Top achievements
Rank 1
Answers by
PetarP
Telerik team
Dave
Top achievements
Rank 1
Damyan Bogoev
Telerik team
Share this question
or