| PLEX86 | ||
|
mySQL import text file too big 3062I have no experience with phpMyAdmin so I can't comment here. And Your "mySQL 11.18" version info is indecipherable. What version(s) are you running? Are you porting data between 2 identical versions? If not - beware of your --opt switch. A nickle says you creating something in one version that is not recognized by the other - IF you are porting between different MySQLs. 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... Personally, I always separate backup up of database structures from backing up the data. It makes it easier to keep things straight. I use mysqldump with -d to get data structures only. If I want to restore or recreate a database. I start empty (no tables) and execute the script created by mysqldump. mySQL import text file too big 3063 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... And I don't use mysqldump at all for the data. I use SELECT * INTO OUTFILE 'sometable.dat' to backup data and a corresponding LOAD TABLE INFILE('sometable.dat') to restore the data. These files are substantially smaller anyway, since they don't need to carry all the SQL syntax (INSERT, VALUES and such). Just a clean tab delimited (or comma, or what have you) text data table that is portable. 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 certain lines... I don't know of an import file size limit and I am having difficulty believing this can be the problem. You mention that the file size of your phpMyAdmin dump is substantially larger than what you get from mysqldump. *Clearly*, each is throwing something different at MySQL when you try to import. You *still* need to isolate "line X" (where MySQL is choking!) if you really want to know what's shaking. MySQL is telling you where it's having a problem. You owe it to yourself to look at that spot! Thomas Bartkus
|
||||
mySQL import text file too big 3063 Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||