We create a package to hold our cursor type, look a the top of our generated stored procedure output, it's at the very top.  But we don't put our procs in a package you are correct. I'm not sure honestly what the syntax would look like in a package. Either way we just missed this release so a quick fix probably isn't forthcoming.

[modified]

Can you do some kind of trace in Oracle and show us what the differnence is between pure ADO.NET code that works and the EntitySpaces that fails? We might be able to use the options like Ignore Schema / Ignore Catalog in the Generated master to control this?

ouuuccchh (in my best ET voice).   I'll try.

 
I'm not sure that I know what is pure ADO.NET. Would you consider the code posted above http://community.entityspaces.net/forums/permalink/3768/3675/ShowThread.aspx#3675 to be pure ADO.NET?  If so, I'll attempt to get  a trace for you.

 BUT, You do have an example of a call to a procedure in a package that returns a refcursor

MYGENERATION.esAggregateTestLoadByPK

Maybe if I can see that that portion of the package, I can figure out what syntax it takes to make that type of call work. 

Curtis

Maybe if I can see that that portion of the package, I can figure out what syntax it takes to make that type of call work. 

Just run our Oracle Stored Procedure template on one of our tables, it's all right there in the output window after you run it in MyGeneration.

I think you're trying to confuse me :)

I want to see the procedure esAggregateTestLoadByPK located in your package MYGENERATION.  It's not a generated procedure.

It's just the LoadByPrimary key stored proc for our AggregateTest table, here it is.

CREATE OR REPLACE PROCEDURE "MYGENERATION"."proc_AggregateTestLoadByPrimaryKey"
(
    pID IN "AggregateTest"."ID"%type,
    outCursor OUT "MYGENERATION".ENTITYSPACES.sqlcur
)
IS
BEGIN
    OPEN outCursor FOR
	SELECT
		"ID",
		"DepartmentID",
		"FirstName",
		"LastName",
		"Age",
		"HireDate",
		"Salary",
		"IsActive"
	FROM "AggregateTest"
	WHERE
		"ID" = pID
;
END ;
/