SqlServer .Net2 RetrievalStoredProcedure CallAsQuery

Posts   
 
    
frakevich
User
Posts: 6
Joined: 03-Sep-2009
# Posted on: 31-Mar-2010 19:42:25   

Hi, the .Net 2.0 template for Sql Server retrievalProcedures The Get[ ]CallAsQuery is missing the Output parameters loop in the function parameter list.

And the parameter type might need to be set to InputOutput as in other places instead of just Output, but that I am not sure about.

Thank you

daelmo avatar
daelmo
Support Team
Posts: 8245
Joined: 28-Nov-2005
# Posted on: 01-Apr-2010 04:19:03   

Are you actually referring to a bug or a request? What is your LLBLGen version and runtime library version? (http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=7717)

David Elizondo | LLBLGen Support Team
frakevich
User
Posts: 6
Joined: 03-Sep-2009
# Posted on: 01-Apr-2010 05:08:09   

I'd say its a bug. Llblgen 2.6, .net 3.5 c#.

Also, another question along these lines, I modified the template myself, restarted llblgen, but the generated code seemed like it did not see my changes. Is there an alternative location for the templates? The template I was adding changes to is in my installation folder: C:\Program Files\Solutions Design\LLBLGen Pro v2.6\Templates\SqlServerSpecific\Net2.x\C#

Thanks Filipp

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39951
Joined: 17-Aug-2003
# Posted on: 01-Apr-2010 09:45:34   

The output parameters are missing as they can't be returned back. The query is called at a later time, but how do you want to get the values back?

Frans Bouma | Lead developer LLBLGen Pro
frakevich
User
Posts: 6
Joined: 03-Sep-2009
# Posted on: 01-Apr-2010 16:48:56   

I see what you mean, but since they are byref parameters I thought that there was a way to reassign values to them. But I can take a no for an answer wink P.S. I studied my own code that made use of a modified version of that RetrievalProcedures function (which took a byref parameter) and I am manually setting the parameter direction and retrieving the parameter value from the parameters collection. I just did not notice this right away since the code stopped compiling after regeneration.