Re: No line number with RaiseError in DBD::Sybase

On Wed, Jun 18, 2008 at 02:14:06PM -0700, Douglas Wilson wrote:
With RaiseError or PrintError set, if DBD::Sybase throws an error, the
error message does not indicate what line number of the program that the
error was on ... or what program/module that the error was in.

I'd guess that that's because sybase error messages tend to end with a
newline character.

Hopefully that's a simple fix for Michael to get into the next release.
You could always send a patch to help out...

Tim.
.

Relevant Pages

  • Re: SBS 2003 - Hal.dll Getting Corrupt
    ... Sorry Michael, I was on vacation and I didn't check any of my emails until ... I ran a chkdsk the first two times that this happened to me ... sometime this weekend and see is there is any type of error message. ... "Windows could not start because the following file is missing or corrupt: ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Boot problem, copied Master
    ... Michael Solomon wrote: ... > Place the compressed image file on the master or on a separate partition on ... For the record, on the Slave Drive, I have ... I get error message about destination being in use ...
    (microsoft.public.windowsxp.basics)
  • Re: Cannot open or copy word document
    ... You may be able to rescue some text depending ... "Michael" wrote in message ... When I had NT4.0 I copied some word docs to a CD. ... I searched for that error message and what I found did not ...
    (microsoft.public.word.application.errors)
  • Re: [PATCH] ide-cd: fix endianity for the error message in cdrom_read_capacity
    ... still leaves a bug in the error message, ... big-endian value for printk. ... Fix this by using a local variable in machine byte order. ... Bart owns this patch now. ...
    (Linux-Kernel)
  • Re: Shutdown error with ntpd
    ... > whole error message, ... > Michael D. Setzer II - Computer Science Instructor ... directive where you can specify a log file? ...
    (Fedora)