Let me know when you hit over 1GB compressed. =)
> Correct me if i'm wrong, but *surely* if MySQL is
> able to generate a dump file of SQL statements to
> rebuild the current database, then they *should*
> execute flawlessly when doing an import.
Perhaps you could share with us what your msyqldump command is.
> Why is it, that 90% of the time when I recover
> from a dump I have to manually edit my dump file
> because I am almost certain to get errors in the
> SQL execution at several places in the dump file?
>
> The most notable problems are in the
> reconstruction of triggers, but I also have
> problems in even some basic statements such as
> inserts or table definitions.
>
> Am I doing something wrong or is MySQL just not of
> production quality yet?
Oh, its ready and been there. A more detailed report of the exact errors you receive could help a lot.
> On a side note - how does one edit the 200mb dump
> file when it basically hangs pico and brings 'vi'
> to an insufferable crawl. Is there a good set of
> tools for cutting buts out of dump files, or
> importing only certain parts of it?
sed, awk, grep, etc. But, there should not be errors.
Brian Moon
Phorum Dev Team
----------------------------------------------------------
MySQL.com uses Phorum. Why don't you?
http://www.phorum.org/
----------------------------------------------------------