FreeTDS Development Group

["James K. Lowden" <jklowden AT freetds.org>]

On Fri, 2 Mar 2012 16:43:39 -0500
"Bower, Wayne (Wayne)" <Wayne.Bower AT lsi.com> wrote:

> Essentially the issue appears to be related to using 'SET NOCOUNT ON'
> in a stored procedure. The script creates a procedure and executes
> it.  The cases that fail issue the message '[unixODBC][Driver Manager]
> Function sequence error (SQL-HY010)'.  To avoid the failure I have to
> either remove 'SET NOCOUNT ON' or move later in the procedure.  Keep
> in mind that this is just a test case to reveal the issue.  In our
> actual code we always start each procedure with 'SET NOCOUNT ON' and
> do much more than shown in this test case.

Is the problem restricted to procedures that pass parameters?  If not,
does bsqldb exhibit the same symptoms?  If so, could you provide just
the SQL?  

If parameters are required to provoke the problem, I would alter
src/odbc/unittests/rpc.c to induce it.  It tried the attached patch;
it did not alter the outcome of the test.  

HTH.  

--jkl

Attachment: odbc.rpc.diff
Description: Binary data