PEPPLER.ORG
Michael Peppler
Sybase Consulting
Menu
Home
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
Freeware
Sybperl
Sybase::Simple
DBD::Sybase
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
FAQs
Sybase on Linux FAQ
Sybperl FAQ
Personal
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: tungw at foliotrade dot com (Winnie Tung)
Subject: RE: Newbie Question on trapping errors
Date: Dec 7 1999 12:17AM

First of all, thanks for reply.
However, if the sql cmd I send is a stored procedure, if this stp does not
exist;
dbexecsql will not return error, non does dbresults.
That's the problem I'm struggling with.

Winnie


> -----Original Message-----
> From: owner-SYBPERL-L@listproc.net
> [mailto:owner-SYBPERL-L@listproc.net]On Behalf Of Michael Peppler
> Sent: Monday, December 06, 1999 6:54 PM
> To: SybPerl Discussion List
> Subject: Re: Newbie Question on trapping errors
>
>
> Winnie Tung writes:
>  > Hi:
>  >
>  > It seems to me that dbexecsql() does not always return
> FAIL on a failed
>  > operation.
>
> dbsqlexec() returns fail if the SQL you sent only has one result
> set. If there are more than one result set, then you need to loop on
> dbresults() and check its return code for FAIL values.
>
> Michael
> --
> Michael Peppler         -||-  Data Migrations Inc.
> mpeppler@peppler.org    -||-  http://www.mbay.net/~mpeppler
> Int. Sybase User Group  -||-  http://www.isug.com
> Sybase on Linux mailing list: ase-linux-list@isug.com
>
>