PHP Classes

Only One Table Backing Up...

Recommend this page to a friend!

      SQL Backup  >  All threads  >  Only One Table Backing Up...  >  (Un) Subscribe thread alerts  
Subject:Only One Table Backing Up...
Summary:I Only Get The First Table in my Database To Back Up
Date:2006-06-02 16:12:45
Update:2006-06-14 15:11:43

  1. Only One Table Backing Up...   Reply   Report abuse  
Picture of NoiseEee NoiseEee - 2006-06-02 16:12:45
Hi there

Despite running the example backupfile verbatim (with my own login/pass obviously), I only get a single table backed up - not my whole database.

Am I missing something?

  2. Re: Only One Table Backing Up...   Reply   Report abuse  
Picture of Richard Munroe Richard Munroe - 2006-06-03 13:36:58 - In reply to message 1 from NoiseEee
All I can say is that it works for me on every database that I have access to. I'm primarily using PHP 4.4.0 on a Debian system. I'd suggest spending some time trying to debug it since there are some fairly substantial incompatibilities between earlier versions of PHP and 4.4.0 (I've found a number of classes that don't work at ALL with earlier versions) and I'm not planning to chase those unless I run into problems personally (I will gladly accept fixes for those environmental problems, however).

There is a loop early on that enumerates the tables in the database, see what's being returned there and let me know. Basically I can't debug it in your environment and have to assume that, since it works here, that there is some sort of environmental problem at your end. It's possible that your PHP environment needs to be reconfigured as well. I typically run allowing PHP substantial resources (much larger than defaults) which could potentially affect the running of the backup script.

My guess is that your version of PHP doesn't honor either persistant connections to mysql OR that it doesn't do the right thing when copying references (both of which I've seen depending on the version and configuration of PHP). If it's the latter, you'll need to figure out what to do to get a "clean" copy of the database object so that you can read the tables without loosing state when attempting to access the meta information about the tables. I forget what I did when I ran into the former, probably tweaked something in the PHP .ini file but I forget (it's been years since I've seen that particular problem).

FWIW, if you're using a Red Hat system <= 9.0 then they are using an old and [somewhat] buggy version of PHP (4.2) as their standard release version. I would suggest upgrading PHP ASAP and trying again. One of my clients rents time on a RH 9.0 box and it's been a real pain since the ISP won't upgrade it without RPMs.

Dick Munroe

  3. Re: Only One Table Backing Up...   Reply   Report abuse  
Picture of Richard Munroe Richard Munroe - 2006-06-11 14:50:49 - In reply to message 1 from NoiseEee
I took a look at the PHP 5 documentation and they've completely changed the reference model used. The net result is the behavior that I relied on:

$a = some object
$b = $a

would result in 2 distinct copies of the object in PHP 4, but only 1 in PHP 5. In PHP 5 the code should look like:

$a = some object
$b = clone $a

which has the same semantics as the previous code.

This will eventually be cleaned up when I get around to it, but until then, the immediate one table problem you're referring to occurs in the while loop:

while ($theTable =& $this->m_dbObject->fetchRow())
$theTableName = $theTable[0] ;

$theDB = $this->m_dbObject ;


If you replace the last line with:

$theDB = clone $this->m_dbObject ;

you should be up and running. There may be other places in the code in which this problem occurs, but fixing those is currently an exersize to the user.


  4. Re: Only One Table Backing Up...   Reply   Report abuse  
Picture of Richard Munroe Richard Munroe - 2006-06-14 15:11:43 - In reply to message 3 from Richard Munroe
This problem has been fixed in the current copy of the code.

For more information send a message to info at phpclasses dot org.