So... I'm trying to export a fairly large database (~10 GB). I've done it
dozens of times before, using scripts on a regular basis. Now, the database is
growing, and lately, every dump file produced has problems. When I try to run
"mysql -u root -p < dump_file.sql", MySQL will fail and return an
I'm stuck again ... and perhaps it's just not designed right, but I
inherited this setup, so if anyone has suggestions on how to make it better,
I'm all ears. This is all one table ...
describe approvals;
+---+--+--+-+-++
| Field
Except that, in my case, both machines are running 5.1.39. Mac "OS X" PPC
64-bit. I tried importing another, different dump file of the same database,
and this time mysql returned a different error:
Sat Nov 21 13:16:20 -- Minas-Tirith :: mysql -u root -p < dump_file.sql
Enter password:
ERROR
Hello and Greetings,
I have an idea for a project that I am putting together and was
wondering about the best way to store the information. I am looking
for suggestions concerning the formatting and storing of information.
I have three different groups that I need to track and use
information. Th
There is a bug in mysqldump that prevents mysql from version 5.0.80 from
importing dumps from a old version of mysqldump.
I had this verified by MySQL support.
You can have a look at this bug: http://bugs.mysql.com/bug.php?id=41486
Cheers
Claudio
2009/11/21 René Fournier
> It's just odd, bec
> DB engines that have their own data dictionary (Innodb, etc) in
addition to
> what is in the .frm could easily be messed up.
Like I said, there are only MyISAM tables in the database, so would
there be any risks associated with my simple approach?
(Also there are no stored procedures because
It's just odd, because that error was on 5.0. I'm running 5.1.39 -- surely
enough time for the MySQL devs to fix it right?
Could it be with extended inserts that the max statement length is greater than
the default 16MB max allowed packet? I'm increasing that value to 256 MB and
going to try ag
DB engines that have their own data dictionary (Innodb, etc) in addition to
what is in the .frm could easily be messed up.
On Sat, Nov 21, 2009 at 10:38 AM, Robinson, Eric wrote:
> I used a simple procedure to rename my MySQL 4.1.22 database, which has
> only My-ISAM tables:
>
> 1. Stopped MySQL
I used a simple procedure to rename my MySQL 4.1.22 database, which has
only My-ISAM tables:
1. Stopped MySQL
2. Renamed the database directory from olddbname to newdbname
3. Started mysql
At this point, I grepped for 'olddbname' and found that many of the old
.MYI files still had references to
