Jesse wrote:
Dan Wilga wrote:
I've been running with InnoDB for the last year; IMHO more
reliable
in case of system crashes where MyISAM tables tend to corrupt more
easily (esp. recordmarkup).
I run a high-volume web site that uses MySQL for some
pretty frequent
tasks, and
At 4:45 PM -0400 10/3/05, Jesse Guardiani wrote:
I found my problem, but I'm not sure how to fix it. Every sunday
morning I shut down my
MySQL database and analyze and repair all tables. This is a trick I
learned from my production
Sys Admin days with MySQL versions 3.23.x.
I don't find that
I've been running with InnoDB for the last year; IMHO more reliable in
case of system crashes where MyISAM tables tend to corrupt more easily
(esp. recordmarkup).
I run a high-volume web site that uses MySQL for some pretty frequent
tasks, and haven't had any data corruption problems.
The
Dan Wilga wrote:
I've been running with InnoDB for the last year; IMHO more reliable in
case of system crashes where MyISAM tables tend to corrupt more easily
(esp. recordmarkup).
I run a high-volume web site that uses MySQL for some pretty frequent
tasks, and haven't had any data corruption
Hello,
Has anyone tried running MythTV with INNODB
tables? I run them at work, and they seem
very reliable.
MyISAM, on the other hand, seems to corrupt
easily. At least once a month I have to fix
a table...
Is INNODB a drop in replacement?
--
Jesse Guardiani
Programmer/Sys Admin
[EMAIL
On 02/10/05, Jesse Guardiani [EMAIL PROTECTED] wrote:
Hello,
Has anyone tried running MythTV with INNODB
tables? I run them at work, and they seem
very reliable.
MyISAM, on the other hand, seems to corrupt
easily. At least once a month I have to fix
a table...
Is INNODB a drop in
