> On the other hand, I still suffer from table corruption with MySQL.
> It still munges my data at a whim just so it doesn't have to throw an
> exception. I still have to do things with temporary tables that
> should be done with a sub-select (we don't run mysql 5 yet, since it
> is too new for me).
Whenever I see something like this, my first thought is "What
tabletype are you using?" InnoDB tables have the same recovery
capabilities as any other ACID-supporting table. MyISAM is the one
that can be corrupted, but you shouldn't be using MyISAM tables for
heavy CRUD. It wasn't designed for that - InnoDB was.
Furthermore, subselects are in MySQL 4.1 which has been out for over 2
years, not MySQL 5.
Rob
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.