I'm trying to determine the best way to back up my MySQL databases in such a
way that they can be easily restored, flexible, and complete. I've
experimented with physically copying the files (with disastrous results).
MySQLDump seems to be the way to go, but I've got two problems with that
which I don't know how to overcome:
1) MySQLDump does not appear to get Procedures, Functions, and Triggers.
What I'm doing right now for this is manually copying those to another file
which I've got, then if I have to restore a database, I have to manually add
the procedures, functions, and triggers back into the database.
2) sometimes, I like to copy just a single table or so out of the backup
file, and restore just that. That's why I really like the way MySQLDump
works, because it creates SQL code that I can simply run to re-create and
restore the records. Problems is that a table/create/insert is one
continuous line, with no line breaks, So, if I've got a table with 100,000
records, I cannot copy that table out, because my editor forces a hard line
break at column position 16384, which, of course, corrupts the restore. I
don't know if there are other text editors that will not do this, or even
better, if there is a way to add a hard line break after each inserted
record. I realize this will increase the size of the backup file, but to
me, it's worth it.
Any ideas?
Thanks,
Jesse
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
