[freetds] Status: bcp

Castellano, Nicholas Nicholas_Castellano at acml.com
Mon Dec 22 09:57:19 EST 2003


> From: James K. Lowden [mailto:jklowden at schemamania.org] 
> Sent: Friday, December 19, 2003 11:07 PM
> To: FreeTDS Development Group
> Subject: Re: [freetds] Status: bcp
> 
> 
> On Fri, 19 Dec 2003, "Castellano, Nicholas" 
> <Nicholas_Castellano at acml.com>
> wrote:
> > Huh?  There's an entire class of informational messages 
> with severity 
> > class EXINFO.  Are we talking about the same thing?
> 
> We're talking about the same thing, yes.  
> 
> > It's perfectly legitimate for an error handler to return INT_CANCEL 
> > and expect the program to continue doing what it was doing before.  
> > The semantics are strange, but it's the correct behavior.
> 
> On what theory "perfectly legitimate", maestro?  
> 
> All I'm saying is I can't find anything that tells me under 
> what circumstances a db-lib handler can return INT_CANCEL and 
> expect the calling function to proceed unaffected.  The docs 
> say unequivocally the calling function will return FAIL.  
> 
> I agree with you that we have to be bug compatible, so if 
> behavior strays from documented behavior, the implementation 
> governs.  I'm happy to defer to your experience; I'm just 
> trying to get it right.  

My WAG:  If the severity of the error is EXINFO, then INT_CANCEL will cause
the calling function to proceed unaffected.

I can't back that up with any documentation, since as you say, the
documentation is clear, and as I say, it's clearly wrong.

But it does fit my observations about the behavior of INT_CANCEL, and also
seems to be a "reasonable" place to draw the line.

--nick
-----------------------------------------
The information contained in this transmission may contain privileged and confidential information and is intended only for the use of the person(s) named above. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender immediately by reply e-mail and destroy all copies of the original message. Please note that we do not accept account orders and/or instructions by e-mail, and therefore will not be responsible for carrying out such orders and/or instructions.




More information about the FreeTDS mailing list