RE: SQL errors not making it back to Perl

On Friday, September 10, 2010 3:58 AM, Martin J. Evans wrote:

> On 09/09/10 21:20, Roode, Eric wrote:
> > On Thursday, September 09, 2010 4:14 AM, Martin J. Evans wrote:
[...]
> >>
> >> You could send me a level 15 trace and I might see something but it
> >> looks like raiserror in your case is not raising an error.
[...]
> > 
> > I don't know what a "level 15 trace" is, but I'd be interested in
> > doing it if it might shed some light on what's going on.
> > 
> > -- Eric
> > 
> 
> See http://search.cpan.org/~mjevans/DBD-ODBC-1.24/ODBC.pm#Tracing
> 
> I suggest you add:
> 
> use DBD::ODBC;
>
DBI->trace(DBD::ODBC->parse_trace_flags('odbcconnection|odbcunicode'));
> 
> to the start of your script then do something like:
> 
> set DBI_TRACE=15=x.x
> 
> from the command line before running your script. The trace output
> will go to the file x.x.
>
> Don't send the trace to the list - it will probably be quite large
> and will get filtered anyway.

Okay, I did that, and I got a nice verbose trace.  I'm no expert here,
but I don't see anything that looks suspicious in it.  At first I was
startled by this message:

    !!DBD::ODBC unsupported attribute passed (RaiseError)

but then I saw it with other attributes (Username, e.g.), so I figured
that DBI was handling this attribute.  (Am I right?)

Anyone who would like to look at the log (and, I hope, to show me what
I'm missing!) can see it at

    http://nopaste.gamedev.pl/?id=8071
or
    http://cl.ly/1c7e22e086fb0d3556fa

I would appreciate it.

Thanks,
-- Eric