Re: Data import problems
Perhaps you mean 'sed'. Filipe Tomita wrote: tks for reply but i dont have acces to original database... the dump file not generated from me.. Someone tell me about "SAD" command to replace table name to correct name but i dont find anything about it. On 9/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Filipe Tomita <[EMAIL PROTECTED]> wrote on 09/09/2005 04:37:01 PM: Hi people, I having problems to import a dump generated via mysql dump in mysql 4.0.20slackware version to a mysql 4.1.14. The dump generated with other table name (Insert into temp, temp2 , temp3) in 20 sql large (420mb.) sql files. I tried LOAD DATA INFILE but data not inserted correctly, someone help-me?? tks. Tomita If you look at the output from mysqldump, you will realize that it is just a series of SQL statements. Execute them with your command line client just as you would any other SQL script file. mysql database -u username -p < dumpfile.txt or use the source or . commands if you are already in the CLI mysql>source dumpfile.txt Where you will run into problems is if you didn't specify a max_packet_length WHEN YOU MADE THE DUMP. That option tells mysqldump just how long the longest single statement can be. If you try to run a dump file that contains a statement that exceeds the max_packet_length setting on your server, it will fail silently (server gone away). If you failed to dump with a maximum set, your options are to increase the MAX_PACKET_LENGTH on the server to accept the longest single statement in your dump file or to edit your dump by hand and break your long statements into shorter ones or both. Shawn Green Database Administrator Unimin Corporation - Spruce Pine -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Data import problems
tks for reply but i dont have acces to original database... the dump file not generated from me.. Someone tell me about "SAD" command to replace table name to correct name but i dont find anything about it. On 9/9/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > Filipe Tomita <[EMAIL PROTECTED]> wrote on 09/09/2005 04:37:01 PM: > > > Hi people, > > > > I having problems to import a dump generated via mysql dump in mysql > > 4.0.20slackware version to a mysql > > 4.1.14. > > The dump generated with other table name (Insert into temp, temp2 , > temp3) > > in 20 sql large (420mb.) sql files. > > I tried LOAD DATA INFILE but data not inserted correctly, someone > help-me?? > > > > tks. > > > > Tomita > > If you look at the output from mysqldump, you will realize that it is just > a series of SQL statements. Execute them with your command line client just > as you would any other SQL script file. > > mysql database -u username -p < dumpfile.txt > > or use the source or . commands if you are already in the CLI > > mysql>source dumpfile.txt > > > Where you will run into problems is if you didn't specify a > max_packet_length WHEN YOU MADE THE DUMP. That option tells mysqldump just > how long the longest single statement can be. If you try to run a dump file > that contains a statement that exceeds the max_packet_length setting on your > server, it will fail silently (server gone away). > > If you failed to dump with a maximum set, your options are to increase the > MAX_PACKET_LENGTH on the server to accept the longest single statement in > your dump file or to edit your dump by hand and break your long statements > into shorter ones or both. > > Shawn Green > Database Administrator > Unimin Corporation - Spruce Pine >
Re: Data import problems
Filipe Tomita <[EMAIL PROTECTED]> wrote on 09/09/2005 04:37:01 PM: > Hi people, > > I having problems to import a dump generated via mysql dump in mysql > 4.0.20slackware version to a mysql > 4.1.14. > The dump generated with other table name (Insert into temp, temp2 , temp3) > in 20 sql large (420mb.) sql files. > I tried LOAD DATA INFILE but data not inserted correctly, someone help-me?? > > tks. > > Tomita If you look at the output from mysqldump, you will realize that it is just a series of SQL statements. Execute them with your command line client just as you would any other SQL script file. mysql database -u username -p < dumpfile.txt or use the source or . commands if you are already in the CLI mysql>source dumpfile.txt Where you will run into problems is if you didn't specify a max_packet_length WHEN YOU MADE THE DUMP. That option tells mysqldump just how long the longest single statement can be. If you try to run a dump file that contains a statement that exceeds the max_packet_length setting on your server, it will fail silently (server gone away). If you failed to dump with a maximum set, your options are to increase the MAX_PACKET_LENGTH on the server to accept the longest single statement in your dump file or to edit your dump by hand and break your long statements into shorter ones or both. Shawn Green Database Administrator Unimin Corporation - Spruce Pine
Data import problems
Hi people, I having problems to import a dump generated via mysql dump in mysql 4.0.20slackware version to a mysql 4.1.14. The dump generated with other table name (Insert into temp, temp2 , temp3) in 20 sql large (420mb.) sql files. I tried LOAD DATA INFILE but data not inserted correctly, someone help-me?? tks. Tomita
