PLEX86  x86- Virtual Machine (VM) Program
 Plex86  |  CVS  |  Mailing List  |  Download  |  Linux  |  Newsgroups

mySQL import text file too big 3063


Your Ad Here

Your Ad Here

Thomas Bartkus

are you - one between

Sorry, I did a "mysql -V" and wrote down the wrong info. Source mySQL = 3.23.58 Destination mySQL = 3.23.58

OK, I guess that's not the issue.

backing restore script OUTFILE substantially (INSERT, you)

Zend Development and erroneous buttignment Condition bugs
I'm trying out the Zend Development Environment 4, and for the most part I like it, except for two things. It seems to think...

That's certainly an idea to consider. But how viable is that? For example, in the one database (and we have 5 we need to back up on a regular basis) we have over 30 tables. Would be pretty onerous to do a query export and import for each table. Is that even something than can be automated? I have a cron doing the mysqldump every 30 minutes and sending them to a folder that stores the last 7 days of backups (yeah, that's a lot, but I do that in case there's some terrible event that happens that makes the data invalid for up to 6 days before we realize it.) Now that I think about it, I suppose I could make a shell executable PHP script that can be croned. Anyway....

your mysqldump. to

Yeah, because I was able to import a backed up file that was 4 times larger than the automated exports, successfully, I have ruled out size being an issue. Comparing the two files, the 60MB file I get from mysqldump and the 250MB file I get from phpMyAdmin, I can't see anything blatantly different. Both have the DUMP-CREATE commands for all the tables, and from a superficial look, it appears that the format of the inserts are the same. The only thing I can think of is missing data...but even if that's the case, since the 60MB mysqldump file has commands to create all the tables, it SHOULD do at least THAT much.

Well, also, if there IS missing data, doesn't make for a viable backup.

really a

Yeah, new twist in that topic. It appears that that one mysqldump 60MB version I grabbed yesterday to test with, was actually an incomplete file. Only by about 2 MB though. I copied it out from the backup dir before it was actually finished dumping. How unluck is that. =

Zend Development and erroneous buttignment Condition bugs
Liam, I'm not familiar with the Zend IDE. I'm downloading now for a test drive. However, I tried looking at your problem from a code perspective. I pulled this example from...
can't get htaccess in Apache to work
This is driving me nuts. No matter what I do, what changes I make in httpd.conf, how I make .htaccess...

Anyway, I tried it again today with a completed mysqldump file and I don't get the error. Although, it's STILL only creating some of the tables and is a quarter the size of the phpMyAdmin export.

Well, thanks for replying. I appreciate the tips! Liam



Your Ad Here

List | Previous | Next

Zend Development and erroneous buttignment Condition bugs

Linux groups from Newsgroups

The #1 Usenet Provider on the Internet

mySQL import text file too big 3062