List:General Discussion« Previous MessageNext Message »
From:Daevid Vincent Date:September 2 2009 9:29pm
Subject:RE: Problem w/ mysqldump
View as plain text  
If it's MYISAM tables, then they're all self contained in folders in
/var/lib/mysql/spreadsheets. Remember that if you do copy the files, to shut
down mysql first or you could copy corrupt files.

If you're using INNODB, then the schema is in that folder, but the actual
data is in the /var/lib/mysql/ib* files. Along with all the other INNODB
databases you may have on the system -- all mashed 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:victorsubervi@stripped] 
> Sent: Wednesday, September 02, 2009 1:43 PM
> To: Daevid Vincent; mysql@stripped
> 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 was 
> actually stored,
> in what file, I could copy it over to another computer. Any ideas?
> Thanks,
> V
> 
> On Wed, Sep 2, 2009 at 4:09 PM, Daevid Vincent 
> <daevid@stripped> wrote:
> 
> > While not python, maybe this bash script will give you some clues?
> > http://daevid.com/content/examples/daily_backup.php
> >
> > Also, please don't cross post to multiple lists. Not 
> everyone on this mySQL
> > list is on the python list and vice versa. It's just bad netiquette.
> >
> > > -----Original Message-----
> > > From: news [mailto:news@stripped] On Behalf Of Emile 
> van Sebille
> > > Sent: Wednesday, September 02, 2009 7:18 AM
> > > To: mysql@stripped
> > > Cc: python-list@stripped
> > > Subject: Re: Problem w/ mysqldump
> > >
> > > 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 does the
> > > same.
> > >
> > > Then read the mysqldump docs for the command arguments 
> and supply the
> > > database name...
> > >
> > > Emile
> > >
> > >
> > > > This nicely creates the file...but the file is empty! The
> > > database exists
> > > > and has lots of data, I double-checked it. If there is
> > > nothing wrong with my
> > > > code, is there some way to do the same thing from within
> > > MySQL? Can I at
> > > > least print everything to screen and copy it? Where would I
> > > find my database
> > > > in Windoze?
> > > > TIA,
> > > > Victor
> > > >
> > >
> > >
> > > --
> > > MySQL General Mailing List
> > > For list archives: http://lists.mysql.com/mysql
> > > To unsubscribe:
> > > http://lists.mysql.com/mysql?unsub=1
> > >
> >
> >
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe:
> > http://lists.mysql.com/mysql?unsub=1
> >
> >
> 

Thread
Problem w/ mysqldumpVictor Subervi2 Sep
  • Re: Problem w/ mysqldumpEmile van Sebille2 Sep
    • RE: Problem w/ mysqldumpDaevid Vincent2 Sep
      • Re: Problem w/ mysqldumpVictor Subervi2 Sep
        • RE: Problem w/ mysqldumpDaevid Vincent2 Sep
          • Re: Problem w/ mysqldumpVictor Subervi2 Sep