Can a manually-defined persistent class be used as the return type of a stored procedure?

[Chris Jansen]

Hi,

I have a few stored procedures whose results do not map to a table in the database. In situations like this, it looks like the options are to retrieve the data from an object array that is returned, or create an empty view on the database and use it as the return type.

Is it possible to manually create a persistent class in the data model that does not exist in the database, and can be used as the return type for a stored proc?

Thanks.
Chris

[Zoran]

Hi Chris Jansen,

This question has been answered in the support thread you have started on this topic.

Kind regards,
Zoran
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Zsolt]

I have a same issue with mapping stored procedure result to entites. Is the answer avialable to Chris' question?

[Zoran]

Hi Zsolt,

Defining a custom persistent class to preserve the results of a stored procedure is not currently supported by OpenAccess. You can define your class(non persistent) and have your own materialization logic as a workaround. I think that the easiest way to automate the workflow with OpenAccess would be to create database view that resembles the returned values by the stored procedure and then use that view as the return type of the stored procedure.

Best wishes,
Zoran
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.