ar0n, I don't see your problem offhand, but have you tried the DBI->trace method? That should tell you exactly what is going on under the hood. I assume that you've already printed out your SQL and all that jazz.

From the docs:

DBI->trace($trace_level)
DBI->trace($trace_level, $trace_filename)


DBI trace information can be enabled for all handles using 
the trace DBI class method. To enable trace information for 
a specific handle, use the similar $h->trace method 
described elsewhere. 

Trace levels are as follows: 

  0 - Trace disabled.
  1 - Trace DBI method calls returning with results or errors.
  2 - Trace method entry with parameters and returning with results.
  3 - As above, adding some high-level information from the driver
      and some internal information from the DBI.
  4 - As above, adding more detailed information from the driver.
      Also includes DBI mutex information when using threaded Perl.
  5 and above - As above but with more and more obscure information.

I assume you knew about that, but it's the last ditch method that I use when I'm having serious DBI issues. I've never needed a trace level above 3.

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.