Print Page | Close Window

Store procedure returning multiple dataset

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2010
Forum Discription: For .NET 4.0
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=2643
Printed Date: 30-Jul-2026 at 2:24am


Topic: Store procedure returning multiple dataset
Posted By: pponzano
Subject: Store procedure returning multiple dataset
Date Posted: 28-Apr-2011 at 3:28am
Hello,
I'm evaluating your product and got a question about a store procedure I wish to use in a SL demo project... my stored procedure returns 8 dataset but mapping with EDMX a complex type only returns me the first... how can I resolve this?
 
Thanks
Paolo


Replies:
Posted By: robertg
Date Posted: 28-Apr-2011 at 3:59pm
Paolo,

Could you please post the code where you're using this stored procedure, and if it's not too long or sensitive, the stored procedure itself? That will be a good start for figuring out what's going on.

-- Robert

Posted By: pponzano
Date Posted: 29-Apr-2011 at 1:16am
Hello Robert,
consider a simple store that executes

SELECT

top 10* FROM TABLE1

SELECT

TOP 10* FROM TABLE2

when I generate the complex type I get only the column of the first Table1, am I doing something wrong?

Posted By: robertg
Date Posted: 02-May-2011 at 3:00pm
Paolo,

Oh, I see what's going on here. The problem here is that EF itself doesn't support queries which return multiple resultsets like that; understanding how to organize unrelated data like that would likely be extremely difficult for an automated process. Because EF does not support this, neither does IdeaBlade.

Sorry,
Robert

Posted By: pponzano
Date Posted: 03-May-2011 at 12:34am
no problem Robert... I'll continue evaluating your product and if got other question will ask you... have u got a comparative with Telerik's OpenAccess?
Thanks

Posted By: ting
Date Posted: 05-May-2011 at 2:59pm
Hi Paolo,

The Entity Framework is now the standard for .NET data access, so OpenAccess is really competing against that. DevForce adds a lot to the Entity Framework like client-side caching, full n-tier LINQ, dynamic queries, multiple datasources, etc., but the fundamental decision is still whether you want to standardize on EF vs OpenAccess.


Print Page | Close Window