Re: Running a procedural query ?

Other ideas:

Try "SET NOCOUNT ON" at the top of your script, sometimes that results 
in funky stuff in the ODBC protocol, where SQL returns the rowcounts of 
your inserts/updates as many recordsets. (ie "1 rows affected")

Try using "SET" instead of "SELECT" to set variables in your t-sql (ie 
"SET @result = -1" instead of "SELECT @result = -1")

On 03/06/2013 02:47 PM, Russ Tyndall wrote:
> The issue is that CLSQL currently only supports getting the first 
> result set (of the first statement).  I'm not sure whether this is an 
> issue with the ODBC layer or all the layers (probably all of them 
> though).  While problematic, this can usually be worked around by 
> declaring and calling a stored procedure instead.
On first glance it seems like you're only intending to return one 
result, so you should be able to get around the "one resultset" limitation.

HTH,
Ryan

_______________________________________________
CLSQL mailing list
[email protected]
http://lists.b9.com/cgi-bin/mailman/listinfo/clsql