Re: Problem with huge sql-dump

2001-10-27 Thread Johan Nagels
t; Sent: Saturday, October 27, 2001 6:36 PM Subject: Re: Problem with huge sql-dump > > Are the statements ended properly? > > like...insert into table (values etc); > > Some db's will dump with no semicolon on the end...will give you > an error on the second line. >

Re: Problem with huge sql-dump

2001-10-27 Thread Mike
I've had that problem before. It's usually a problem with the max upload size set in the php.ini or something. My suggestion would be, if you can get into the mysql console on the server. Like so: [mike@sherman mike]$ mysql -p Enter password: Welcome to the MySQL monitor. Commands end with ;

Re: Problem with huge sql-dump

2001-10-27 Thread eejack
Are the statements ended properly? like...insert into table (values etc); Some db's will dump with no semicolon on the end...will give you an error on the second line. eejack 091120010850 At 06:28 PM 10/27/01 +0200, Johan Nagels wrote: >Hi, > >I'm trying to import a huge SQL-dump (generated

Problem with huge sql-dump

2001-10-27 Thread Johan Nagels
Hi, I'm trying to import a huge SQL-dump (generated by another program). The statements are correct because if I excute them one-by-one no error is generated. However if I upload them all at once (thru phpMyAdmi or Free Mascon) I always get an error somewhere at te second line. Btw. in the dump t