On Mon, Apr 25, 2005 at 08:15:52AM -0700, Joel Stevenson wrote: > >That's odd. You've not stated the DBI or DBD::Oracle versions. > > > >Try using trace (level 4) with a recent version of the DBI > >to see what the DBI thinks is happening to the error status. > > > >Tim. > > Hi Tim, thanks for the reply. > > I'm running DBI v1.48 and DBD::mysql v2.9006. I've distilled the > problem down into its simplest test case and it looks to be specific > to the DBD::mysql driver or the database server itself (MySQL > v4.0.20). The error does not occur when running the code against the > PostgreSQL driver and database. > > When using trace at level four I can see that the last 'table does > not exist' error is being 'CLEARED by call to fetchrow_hashref' as > the while loop expression is evaluated, but that the fetchrow_hashref > is receiving that exact error on execution, despite not operating on > the non-existant table at all. > > ... > > !! ERROR: 1146 CLEARED by call to fetchrow_hashref method > -> fetchrow_hashref for DBD::mysql::st > (DBI::st=HASH(0xa3cf894)~0xa1407e0) thr#a03e220 > 1 -> FETCH for DBD::mysql::st (DBI::st=HASH(0xa1407e0)~INNER > 'NAME') thr#a03e220 > > ... > > > So it seems like the error is either not truly getting cleared in the > DBD code or that the MySQL database itself is somehow holding onto it > and re-issuing it on the next statement (regardless of what that > statement is.) Very strange.
Can you post the next few lines from the trace, upto just after fetchrow_hashref returns? Tim.
