Re: It's a bad day here...

2012-03-30 Thread Martin J. Evans
On 29/03/12 22:45, Bruce Johnson wrote: another odd error: [for Statement select distinct a.cn, a.email from admins a, resourceadminaffil r, resources r2, adminaffil a2, affils a3 where a.pid = r.pid and r.resource_id = r2.resource_id and a.pid = a2.pid and a2.affil_id = a3.affil_id and

RE: It's a bad day here...

2012-03-30 Thread John Scoles
Are you selecting Lobs or Blobs?? Could be an issue. Crank up the ora_verbse to 15 to get everything. It would do an extra select to get any lob types. I will have to have a look at the full thread sometime tomorrow. Cheers John Subject: Re: It's a bad day here... From: john

Re: It's a bad day here...

2012-03-30 Thread Bruce Johnson
Oh man this is embarrassing :-) A sharp-eyed reader pointed out that I was not doing what I thought I was doing! I noticed the following (edited for emphasis): foreach $i (@resources){ $csr_prefapp-execute($i) $csr_prefapp-fetchrow()) if (!$have_pref){

It's a bad day here...

2012-03-29 Thread Bruce Johnson
another odd error: [for Statement select distinct a.cn, a.email from admins a, resourceadminaffil r, resources r2, adminaffil a2, affils a3 where a.pid = r.pid and r.resource_id = r2.resource_id and a.pid = a2.pid and a2.affil_id = a3.affil_id and a3.affil_code in ('1901','PHRM') and

Re: It's a bad day here...

2012-03-29 Thread Bruce Johnson
On Mar 29, 2012, at 2:45 PM, Bruce Johnson wrote: another odd error: Accidentally clipped off the actual error: DBD::Oracle::st fetchrow failed: ERROR no statement executing (perhaps you need to call execute first) [for Statement select distinct a.cn, a.email from admins a,