[freetds] 0.63 Release Candidate 1
Thompbil18 at aol.com
Thompbil18 at aol.com
Mon Nov 29 17:10:55 EST 2004
Guys,
>> 3) 744992
>>
>> Alas, the bug as identified by Arnar Birgisson is still there.
>> As any solution to this will affect core dblibrary results processing,
>> I'd rather give it a thorough workover.
>> Can I have a couple of days to work on this ?
>Naturally. We'll just make it part of 0.64, if that's OK by you.
Alas,
This is probably more serious than I previously thought. It's come about from
a dblib patch I submitted a while ago (dblib v 1.170 - v1.171). It would
mean a client program wouldn't get told about *any* empty result set that was
returned from within a stored procedure call. Although none of the unit tests
trap this condition, I for one couldn't use dblibrary in it's current state.
Fortunately, I have a patch for this, which I'll submit tomorrow. Although it
does rework dbresults() quite significantly, it makes the processing much
easier to understand and I have tested it pretty thoroughly.
Sorry guys, but better late than after a formal release I guess.
Bill
More information about the FreeTDS
mailing list