Re: [PHP] mysqldump
[email protected] (David Hutto)
| Newsgroups | php.general |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Aug 17, 2010 at 3:04 PM, Robert Cummings <[email protected]> wrote: > On 10-08-17 03:00 PM, David Hutto wrote: >> >> On Tue, Aug 17, 2010 at 2:55 PM, Robert Cummings<[email protected]> >> wrote: >>> >>> On 10-08-17 02:45 PM, Mari Masuda wrote: >>>> >>>> On Aug 17, 2010, at 11:40 AM, tedd wrote: >>>> >>>>> At 2:17 PM -0400 8/17/10, Robert Cummings wrote: >>>>>> >>>>>> On 10-08-17 02:08 PM, tedd wrote: >>>>>>> >>>>>>> Hi gang: >>>>>>> >>>>>>>> At 6:11 PM -0400 8/13/10, Daniel P. Brown wrote: >>>>>>>> Easiest method, from the command line on the server from which >>>>>>>> you >>>>>>>> want to dump the database: >>>>>>>> >>>>>>>> mysqldump -u user -p database_name> outfile.sql >>>>>> >>>>>> Command is wrong... should be: >>>>>> >>>>>> mysqldump -u user -p password database_name> outfile.sql >>>>> >>>>> >>>>> I did catch that, but did not correct it in my post (considering it was >>>>> a >>>>> direct quote). >>>>> >>>>> ------- >>>> >>>> Actually, >>>> >>>> mysqldump -u user -p password database_name> outfile.sql >>>> >>>> is also the incorrect command. When providing the password in the >>>> command, there should not be a space between the "-p" and the actual >>>> password. Try >>>> >>>> mysqldump -u user -ppassword database_name> outfile.sql >>>> >>>> and see if that gets you anywhere. >>> >>> That's actually funny... I never put spaces in for the user or password >>> when >>> using the short parameter method and had quickly tried with the space >>> before >>> posting >> >> 'Playful with passwords the hacker does not expect', says yoda > > I can't wait for 2050 when they release the new Star Wars super duper master > awesome director's milk-it edition with 3 seconds of Yoda smoking a > cigarette! But they'll put it in a pretty 'Happy meal', with lighter included. > >>:) > > Cheers, > Rob. > -- > E-Mail Disclaimer: Information contained in this message and any > attached documents is considered confidential and legally protected. > This message is intended solely for the addressee(s). Disclosure, > copying, and distribution are prohibited unless authorized. >