Skip to Content.
Sympa Menu

freetds - Re: [freetds] Issue with return status from stored procedure withawarning message.

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Glenn, Chris" <Glenn AT addsys.com>
  • To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] Issue with return status from stored procedure withawarning message.
  • Date: Tue, 9 Jan 2007 10:30:54 -0500

> -----Original Message-----
> From: freetds-bounces AT lists.ibiblio.org [mailto:freetds-
> bounces AT lists.ibiblio.org] On Behalf Of Reid, Roger L.
> Sent: Tuesday, January 09, 2007 10:03 AM
> To: FreeTDS Development Group
> Subject: Re: [freetds] Issue with return status from stored procedure
> withawarning message.
>
> I do a lot more db-lib than ct-lib, but isn't it up to the error
handler
> in your app to ignore that severity/error combo and pass control back
to
> the
> point immediately after the error was generated?
>
> app calls sp
> sp generates error
> control goes to apps error handler
> error handler says
> for that error/severity
> return 0
> control passes back to next line of your sp
>
> Or have I done my usual complete misunderstanding of your question and
> issue?
>
> roger reid (not a freetds guru, just a long time user)

Sorry - this is confusing - here are the application steps;

1)App calls sp

2) Sp begins a transaction

3) Sp completes and uses the 'return @variable' to the send back
a value to the App

4) App receives the 'error' code which it does ignore, but the 'return
@varaible' value is not set (it is zero).

If step '2' does not occur, then my App does get the 'return' code.
Therefore, my assumption is that the FreeTDS routine is getting the Sp
status code and ultimately skips the receiving logic for the 'return'
code.

Chris

>
> > -----Original Message-----
> > From: Glenn, Chris
> > Sent: Tuesday, December 19, 2006 2:23 PM
> > To: 'freetds AT lists.ibiblio.org'
> > Subject: Issue with return status from stored procedure with a
warning
> > message.
>
> > When the 'begin tran' is executed, an error code 266 is generated
> > (Transaction count after EXECUTE indicates that a COMMIT of ROLLBACK
> > TRANSACTION statement is missing...) with a severity level of 16.
> > According to Microsoft's documentation (link below), this
> > error code is
> > just a warning message and can be ignored.
> > http://msdn2.microsoft.com/en-us/library/aa258721(SQL.80).aspx
> >
> > What appears to be happening is that the return status is never
> > processed and passed back to my CT-Lib application (I assume)
> > because of
> > the error code 266.
> >
> > I've attached the excerpt from the debug log when calling the stored
> > procedure with the 'begin tran' mode and without.
> >
> > Chris Glenn
> > <<SP with begin trans.txt>> <<SP without begin trans.txt>>
> >
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds



  • Re: [freetds] Issue with return status from stored procedure withawarning message., Glenn, Chris, 01/09/2007

Archive powered by MHonArc 2.6.24.

Top of Page