Ok, I follow that, in future when moving databases I will use mysqldump.
However, I still wish to know why moving the databases by duplicating the
files & directory structure does not work. This is 100% repeatable and I
can't see why (unless file(s) exist I am not copying).
If for some reason sql stops responding / my server dies I will want the most
recent copy of the sql databases, this will always be /var/lib/mysql/ & if I
can access it on the disk, I want to know I can recover it.
I don't mean to sound ungrateful to those who are trying to help me, I just
need to grasp an understanding of what is causing my problem & why.
mysqldump has helped me & solved moving my databases, however I can still
recreate the original problem & still do not understand it.
With Thanks,
Steve.
---
On Tuesday 07 August 2001 17:10, you wrote:
> Dear Steve,
>
> > (eg adding "drop table columns_priv; before the CREATE TABLE
>
> columns_priv;
>
> You can use various options for mysqldump, like --add-drop-table. This
> will add a drop table statement :)
>
> Anyway, it's always a good idea to re-create tables and their data. One
> reason: By default, mysqldump will add TYPE=MyISAM to every create table
> statement, so old ISAM tables will be set up with the new (and better)
> MyISAM format. Another reason: Tables will automatically be in
> "optimized" state.
>
> Regards,
>
> --
> Stefan Hinz
> Geschäftsführer / CEO iConnect e-commerce solutions GmbH
> # www.js-webShop.com www.iConnect.de
> # Gustav-Meyer-Allee 25, 13355 Berlin
> # Tel: +49-30-46307-382 Fax: +49-30-46307-388
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php