> -Original Message-
> From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 07, 2003 8:41 AM
> To: 'Markham, Richard'; [EMAIL PROTECTED]
> Subject: RE: server messages
>
>
> >
> > How do I trap the db server messages that result fro
al Message-
From: Jeff Urlwin [mailto:[EMAIL PROTECTED]
Sent: Friday, March 07, 2003 8:41 AM
To: 'Markham, Richard'; [EMAIL PROTECTED]
Subject: RE: server messages
>
> How do I trap the db server messages that result from the sql
> I pass to the database?
>
What dat
>
> How do I trap the db server messages that result from the sql
> I pass to the database?
>
What database are you using?
Which perl module are you using?
For example, Oracle and DBD::Oracle had/has a way to get dbms_output data.
perldoc DBD::Oracle, looking for dbms_outp
On Thu, 2003-03-06 at 12:30, Markham, Richard wrote:
> How do I trap the db server messages that result from the sql I pass to the
> database?
Depends.
With DBD::Sybase you can use the syb_err_handler attribute (check the
man page).
Michael
--
Michael Peppler
How do I trap the db server messages that result from the sql I pass to the
database?
ne 13, 2002 9:42 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: DBD::ODBC and Sybase/SQL Server server messages
>
>
> I just took a look at DBD::ODBC again after nearly a two year hiatus and
> discovered that this patch I submitted two years ago was never put i
vid Good <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: DBD::ODBC and Sybase/SQL Server server messages
On Fri, Apr 28, 2000 at 10:16:58AM -0700, David Good <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 21, 2000 at 05:32:53PM -0700, David Good <[EMAIL PROTECT
