On Fri, Jun 13, 2008 at 07:29:29AM +0200, Michael Peppler wrote: > Tim Bunce wrote: >> >> I've appended a patch that seems to fix the problem, but I don't know if >> it's doing the right thing in the best way. For example, I tried >> adjusting the "severity > 10" to "severity >= 10" in the code below >> but that caused some tests to fail. > > Normal - there are other severity 10 errors that are not fatal or even > errors as such. Actually I'm surprised that the 5702 error is only a 10, > but I guess this will also be delivered when a DBA kills the connection > from the server side (kill <spid>), and that might not be rated as a really > serious issue. > >> Michael, any chance you could review this and get it (or a better fix) >> released soonish? > > The fix looks reasonable, but I think what you are seeing might be an > indication of a deeper problem when the connection is abruptly lost. > Normally the connection should be marked "dead" in this condition, and > DBD::Sybase should detect it.
Ideally, yes, but it didn't. I'm not sure what you're saying in relation to relasing a new version with this patch. What next? Tim.
