DBI: trace / trace_msg

What's the expected output of the attached script? Steffen trace.pl Description: Perl program

Re: DBD::Oracle and bulk binds via execute_array

Dean Arnold [EMAIL PROTECTED] writes: Does DBI 1.38 have an API that takes an array of rows (which should be the usual end-user interface rather than the more abstract callback method of execute_for_fetch())? If not, it should probably be added, I think I put in a row-wise option in my

Re: DBI: trace / trace_msg (1.38)

DBI 1.38-nothread dispatch trace level set to 9 trace_msg DISPATCH (DBI::db=HASH(0x815cdb4) rc1/1 @3 g0 ima5 pid#12698) at ../trace.pl line 8 - trace_msg in DBD::_::common for DBD::Sponge::db (DBI::db=HASH(0x815cdb4)~0x8217e78 '= 9 =' 9) = 9 =- trace_msg= 1 at ../trace.pl line

Re: DBI: trace / trace_msg (1.36)

... DBI 1.36-nothread dispatch trace level set to 7 DBI 1.36-nothread dispatch trace level set to 6 DBI 1.36-nothread dispatch trace level set to 5 DBI 1.36-nothread dispatch trace level set to 4 DBI 1.36-nothread dispatch trace level set to 3 DBI 1.36-nothread dispatch

bytea escaping?

I got a column of type bytea, and found out that DBD::Pg is complaining when it sees backslashes. I'm using prepare/execute and was under the impression that values added that way were automatically escaped/quoted by DBI, but i have to s/\\//g; to escape the backslashes (do i need to escape

Re: bytea escaping?

On Wednesday, October 8, 2003, at 07:27 AM, Ragnar Hojland Espinosa wrote: I got a column of type bytea, and found out that DBD::Pg is complaining when it sees backslashes. I'm using prepare/execute and was under the impression that values added that way were automatically escaped/quoted by

Re: DBD::Oracle and bulk binds via execute_array

snip So here is my suggestion, based on my work on the DBD::Oracle execute_array patch: DBI interface: The main user-level interface is execute_array(). Four different ways to use: 1. Column-wise, using $sth-bind_param_array() for each column, then $sth-execute_array(\%attr).