Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I was shocked and horrified back in 1998 when I used Oracle and it spewed out a numbered error code that I had to manually look up, even just with a program. I mean, what is this, 1968? The most advanced and expensive database in the world and they can't translate their error codes into human readable strings before spitting it out to the user?

    FWIW I think there *is* some way to configure Oracle to use human readable error codes... but just the thought that this is STILL not the default let alone that it even has to be an option.
    • Well, it spits out the error code and a human readable string. But there are an enormous number of times when the string appears to have nothing to do with the actual problem. (Like some of the obscure parsing errors perl occasionally spits out, but perl is much better at detecting what actually went wrong and telling you.) This site provides a minimal bit of extra assistance in figuring out what one of these errors means.

      Even still, I had a lot of trouble with figuring out what the particular error I

      --
      J. David works really hard, has a passion for writing good software, and knows many of the world's best Perl programmers