Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: michael dot peppler at bnpparibas dot com
Subject: Re: Trigger errors
Date: Feb 14 2006 1:28PM

There are various possibilities.

The first is that you return an error code from your stored proc (ie.
RETURN 1), and then check this return status (CS_STATUS_RESULT). If it is
non-0 then you have an error condition. In general I've tended to return
the same value that I use in the RAISERROR.

The second is that you trap errors in the server callback and raise the
error internally that way.

I also noted that you use $$db_ref for the database handle - this shouldn't
be necessary as a database handle is already a reference...


Internet - 14/02/2006 14:16

Sent by:

To:    sybperl-l


Subject:    Trigger errors

Is there a  "recommended" way to trap errors generated by triggers assuming
the trigger is  using raiserror to signal a problem?

I know that given  the following in my trigger:

        select @msgText =  "Related Key -" + @fieldname +  "- "  +
                 "does not exist in the table " + @desttablename  +
                 " attempt to insert invalid foreign key into table - "  +
                 @sourcetablename + " -Failed "
         raiserror 30053 @msgText
        rollback  tran

that I will get a callback in my client message callback function but  the
question is how do I indicate to the calling perl script that a problem

I have the following routine that executes the stored proc in  question:

sub  exec_sql_nores {
        my $db_ref =  shift;
        my $sql =  shift;
        my ($row_count,  $result_type, $status);

        # establish a handle to the  database
        $row_count =  $$db_ref->ct_execute($sql);
         while (($row_count = $$db_ref->ct_results($result_type)) ==
                 if ($result_type == CS_CMD_FAIL)  {
                         printf STDERR "Error in SQL: %s\n",  $sql;
                 next unless  $$db_ref->ct_fetchable($result_type);
                 my  %data;
                 while (%data = $$db_ref->ct_fetch(CS_TRUE))  {
        return  $row_count;

This routine returns CS_END_RESULTS (-205) as it would if the  stored proc
completed successfully.

Is it a matter  of looking at the error code raised by raiserror and then
returning CS_FAIL from  the message callback?

Thanks for any  help!


The information contained in this communication is intended for the use of
the designated recipients named above.
If the reader of this communication is not the intended recipient, you are
hereby notified that you have received this communication in error, and
that any review, dissemination, distribution or copying of this
communication is strictly prohibited.
If you have received this communication in error, please notify The
Associated Press immediately by telephone at +1-212-621-1898 and delete
this email. Thank you.

This message and any attachments (the "message") is
intended solely for the addressees and is confidential. 
If you receive this message in error, please delete it and 
immediately notify the sender. Any use not in accord with 
its purpose, any dissemination or disclosure, either whole 
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message. 
BNP PARIBAS (and its subsidiaries) shall (will) not 
therefore be liable for the message if modified. 


Ce message et toutes les pieces jointes (ci-apres le 
"message") sont etablis a l'intention exclusive de ses 
destinataires et sont confidentiels. Si vous recevez ce 
message par erreur, merci de le detruire et d'en avertir 
immediatement l'expediteur. Toute utilisation de ce 
message non conforme a sa destination, toute diffusion 
ou toute publication, totale ou partielle, est interdite, sauf 
autorisation expresse. L'internet ne permettant pas 
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce 
message, dans l'hypothese ou il aurait ete modifie.