RAM is Cheap, so is a faster processor.. (InnoDB requires more RAM/Processor then
the simpler MyISAM)..
but your data and downtime is probably a lot more expensive. Its well worth it
going with InnoDB.
For most of what I do, I use a combination of InnoDB and HEAP Tables.
On Tue, Jul 20, 2004
Hi Roy,
If this is a business application, don't go without
transactions and foreign keys. Plain and simple.
Use InnoDB.
With regards,
Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
Server.
Upscene Productions
http://www.upscene.com
> I need so gen
Integrity
Roy,
MyISAM tables also support the FULLTEXT index type, which may be useful,
whereas InnoDB doesn't.
Lachlan
-Original Message-
From: John McCaskey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 20 July 2004 7:50 AM
To: Roy Harrell; [EMAIL PROTECTED]
Subject: RE: Relational Inte
Roy,
MyISAM tables also support the FULLTEXT index type, which may be useful,
whereas InnoDB doesn't.
Lachlan
-Original Message-
From: John McCaskey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 20 July 2004 7:50 AM
To: Roy Harrell; [EMAIL PROTECTED]
Subject: RE: Relational Inte
MyISAM tables are sometimes faster than InnoDB, but for most
applications the difference is going to be negligible. MyISAM tables
also use less disk space (more compressed row format). These are the
only 2 advantages I'm aware of. InnoDB on the other hand offers you
foreign keys and transaction
