together. Hence the need
> for a mysql dump tool ;-)
>
> Mysql dump is the better way to go in either situation.
>
> > -Original Message-
> > From: Victor Subervi [mailto:victorsube...@gmail.com]
> > Sent: Wednesday, September 02, 2009 1:43 PM
> > To:
..@gmail.com]
> Sent: Wednesday, September 02, 2009 1:43 PM
> To: Daevid Vincent; mysql@lists.mysql.com
> Subject: Re: Problem w/ mysqldump
>
> I checked my own backup script from earlier years and
> everything was good.
> You know, if I could simply figure out where the data
t;
> > -Original Message-
> > From: news [mailto:n...@ger.gmane.org] On Behalf Of Emile van Sebille
> > Sent: Wednesday, September 02, 2009 7:18 AM
> > To: mysql@lists.mysql.com
> > Cc: python-l...@python.org
> > Subject: Re: Problem w/ mysqldump
> >
>
ginal Message-
> From: news [mailto:n...@ger.gmane.org] On Behalf Of Emile van Sebille
> Sent: Wednesday, September 02, 2009 7:18 AM
> To: mysql@lists.mysql.com
> Cc: python-l...@python.org
> Subject: Re: Problem w/ mysqldump
>
> On 9/2/2009 3:43 AM Victor Subervi said...
>
On 9/2/2009 3:43 AM Victor Subervi said...
Hi:
I have the following python code:
import os
os.system("mysqldump -u root -pPASSWORD --opt spreadsheets > dump.sql")
First, test this at the system command line -- you'll likely get an
empty file there as well, so calling from within python simply
