[freetds] [unixODBC][Driver Manager]Function sequence error (SQL-HY010)
freddy77 at gmail.com
Sat Mar 3 17:37:27 EST 2012
Another fix is to download the latest patched version.... tomorrow,
just committed :)
Added a test too. Patch at
2012/3/3 Bower, Wayne (Wayne) <Wayne.Bower at lsi.com>:
> The problem appears to be restricted only to procedures with output parameters. We have not encountered the problem with any procedure that only has input parameters.
> We can only avoid the problem by either not using 'SET NOCOUNT ON' or moving 'SET NOCOUNT ON' to a later point in the procedure. This is demonstrated by the different examples in the test case. Also note that having output parameters and 'SET NOCOUNT ON' as the first statement does not guarantee failure as shown with the example that begins with print "\nCreate $proc with input, output, select, init SET NOCOUNT\n";
> Please let me know if you need more information.
> -----Original Message-----
> From: freetds-bounces at lists.ibiblio.org [mailto:freetds-bounces at lists.ibiblio.org] On Behalf Of James K. Lowden
> Sent: Saturday, March 03, 2012 3:16 PM
> To: freetds at lists.ibiblio.org
> Subject: Re: [freetds] [unixODBC][Driver Manager]Function sequence error (SQL-HY010)
> 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.
> FreeTDS mailing list
> FreeTDS at lists.ibiblio.org
More information about the FreeTDS