OK, more debugging, and this is what I have come up with....

The latest_distribution.sql file was NOT created via a mysqldump, but rather
via phpmyadmin export...

The comments from phpmyadmin are denoted with the '#' character....

The comments from a true mysqldump are denoted with the '--' characters...

When doing the command line import with the mysqldump file, it all works
good...

So, I guess this is a warning to anyone who uses phpmyadmin (2.5.6 anyhow)
that if you do an export, it is NOT a valid mysql import... At least not on
my servers ;)

Thanks to everyone who answered so quick!  (and PS - if anyone can confirm
or correct these assumptions, please do let me know.  Thanks!)

On 8/26/04 1:08 PM, "Victor Pendleton" <[EMAIL PROTECTED]> wrote:

> Can you run this from inside the monitor and see if any messages are sent to
> the consol?
> \. latest_distribution.sql
> 
> 
> -----Original Message-----
> From: Mike Morton
> To: [EMAIL PROTECTED]
> Sent: 8/26/04 12:05 PM
> Subject: Mysql command line queries not working....
> 
> I know the subject is not totally descriptive of the problem, but:
> 
> mysql -h ******** -u *** -p*** mikerocks < latest_distribution.sql
> 
> Is producing no results.  I mean none, totally, no errors, nothing.
> 
> The host, user and pass are all correct (of course removed here for
> security
> ;) ) and have the correct permissions.
> 
> The latest_distribution.sql is simply a mysqldump of a database... And I
> have narrowed down the problem to the comments that the dump puts in
> there:
> # phpMyAdmin SQL Dump
> # version 2.5.6
> # http://www.phpmyadmin.net
> 
> Etc...
> 
> Every comment in there aborts the rest of the file... Again, not with
> any
> errors, it just simply stops.
> 
> Mysql on originating server: Ver 11.18 Distrib 3.23.54, for pc-linux
> (i686)
> Mysql on destination server: Ver 12.20 Distrib 4.0.13, for pc-linux
> (i686)
> 
> Additional info:  The mysqldump was created on the originating server.
> There is nothing strange in the mysqldump.  The latest_distribution.sql
> works if imported as an sql query via PhpMyAdmin.
> 
> I need to do this command line (part of an automated setup), so the
> questions are: 
> 
> 1.  Is this a bug or some sort of setting that is messed up or
> something?
> 2.  Can the mysqldump file be created without comments, as removing them
> every time there is a new dump will be tedious to say the least...
> 3.  Am I a total idiot and have missed something dead simple?
> 
> TIA!
> 
> --
> Cheers
> 
> Mike Morton
> 
> ****************************************************
> *
> * Tel: 905-465-1263
> * Email: [EMAIL PROTECTED]
> *
> ****************************************************
> 
> "Indeed, it would not be an exaggeration to describe the history of the
> computer industry for the past decade as a massive effort to keep up
> with
> Apple."
> - Byte Magazine
> 
> Given infinite time, 100 monkeys could type out the complete works of
> Shakespeare. Win 98 source code? Eight monkeys, five minutes.
> -- NullGrey 
> 
> 

--
Cheers

Mike Morton

****************************************************
*
* Tel: 905-465-1263
* Email: [EMAIL PROTECTED]
*
****************************************************

"Indeed, it would not be an exaggeration to describe the history of the
computer industry for the past decade as a massive effort to keep up with
Apple."
- Byte Magazine

Given infinite time, 100 monkeys could type out the complete works of
Shakespeare. Win 98 source code? Eight monkeys, five minutes.
-- NullGrey 



-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to