up vote 1 down vote favorite
share [g+] share [fb]

So here's the thing. On completely different hosts, installations, operating systems and versions of MySQL and PHP (and phpMyAdmin) (but always on a host I'm visiting over the Internet), I've found an interesting situation:

When I try to export a database table (MyISAM or InnoDB) which has "a lot" of data in it, using compression (gzip, zip, it doesn't matter), the file generated isn't complete.

I've put "a lot" in quotes, because it ranges from 1 000 rows to 30 000 rows, depending on the platform. It seems the actual amount is irrelevant.

I have worked around this problem by running mysqldump on the command line and then compressing the output, but I wanted to hear from the community whether this is a known issue, or if it has something to do with the crap bandwidth we have in South Africa, which was recently beaten by a carrier pigeon.

link|improve this question

This one totally belongs on SF – joshhunt Sep 10 '09 at 8:49
feedback

migrated from superuser.com Sep 10 '09 at 8:55

This question came from our site for computer enthusiasts and power users.

1 Answer

up vote 3 down vote accepted

My guess is that it's a script time-out issue with phpMyAdmin, or perhaps a file-size limitation of the underlying webserver.

Update
On a script-by-script bases, you can add set_time_limit(0); at he top and it will override the PHP settings for script timeout to infinite. Any value other than 0 will set it for that many seconds.

link|improve this answer
I thought it was file size limit, but it turned out not to be the case. I'm also inclined to think it's a timeout. – Randolph West Sep 10 '09 at 11:27
Ok, I'm accepting this answer. No one else seems to have any input. – Randolph West Sep 11 '09 at 12:56
hopefully it's right :) – warren Sep 12 '09 at 6:10
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.