FreeTDS Development Group

["Michael Kochetkov" <Michael.Kochetkov AT synartra.com>]

[...]
> > I did some test and I can provide quickly "{call 
> > insertT2(1,?)}" but not
> > "{?=call insertT2(1,?)}" (note "?=" prefix). The reason it's 
> > that mssql
> > do not prepare code that have return inside (you can put 
> > return only in
> > store procedure). Changing code to support correctly store procedure
> > with constants parameters it's too time expensive now...
> Well, let us see if I will be able to think out a workaround. 
I found it to be not that easy indeed due to limitations of my framework -
it heavily relies upon the facility we are talking about. The solution was
born in a hurry and appeared to be pretty ugly, just awful. So I am
hopefully looking forward to your solution. On the other hand I am probably
to file my framework as the anecdote says...

BTW, when I have already ruined my framework to support '?'s everywhere the
idea to make use of "execute ? = procName 3,?,5,?,?" came to me. To my
surprise the FreeTDS was almost capable to do this. And MS ODBC driver
emitted somewhat absolutely unusable to SQL Server. So, you might be
interested to make the FreeTDS to emit the same garbage :).

-
Michael Kochetkov.