By default mysqldump just dumps to stdout.. so you need to > (pipe) it to
a textfile.. the correct syntax, you need to put the database name after
the username/password (after the mysql options)
.. give that a shot.. most likely all the garbage/output wacked out your
session..
On Tue, 10 Feb 2004, Scott Purcell wrote:
> Well, I gave it a shot, but for some reason, the dump caused my command window to
> die, while screaming.
>
> The database is owned by a user with a password, so I typed the following:
>
> mysqldump databasename --user=xxxxxx --password=xxxxxxxx
>
> It started doing something, but like I mentioned, the system begain complaining. I am
> looking at the mysql --help, but I do not see anything about a password, or about where to
> put the files.
>
> Thanks,
>
> -----Original Message-----
> From: colbey@stripped [mailto:colbey@stripped]
> Sent: Tuesday, February 10, 2004 8:24 AM
> To: Scott Purcell
> Cc: mysql@stripped
> Subject: Re: copying blob data to remote box
>
>
> Are you just copying the files? I'd suggest using mysqldump if you are
> not already..
>
>
> On Tue, 10 Feb 2004, Scott Purcell wrote:
>
> > Hello,
> >
> > I am running a DB on a machine in which I am developing on. Then I have been
> copying the contents of ~mysql/data/databasename to another box where I am running my
> code. All the data I modify copies well, and I can run on my production box with no
> problems. Except for binary blob data. When I go to my production box, the blob data does
> not seem to work properly. Are there other files, directories that I need to copy over in
> order to get this to work?
> >
> > The machines are not networked together, I have to move files via CD.
> >
> > Thanks,
> > Scott
> >
> >
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe: http://lists.mysql.com/mysql?unsub=1
> >
> >
>
