Berkeley CSUA MOTD:Entry 41351
Berkeley CSUA MOTD
 
WIKI | FAQ | Tech FAQ
http://csua.com/feed/
2025/05/25 [General] UID:1000 Activity:popular
5/25    

2006/1/11-13 [Computer/SW/Languages/Misc] UID:41351 Activity:kinda low
1/11    What's the difference between an MyISAM and an INNODB table?
        I noticed that you can do FOREIGN KEY and CASCADE on
        INNODB but not MyISAM, but that's the only difference I know.
        \_ MyISAM also doesn't do transactions or row level locking.
        \_ If you don't need those (and more) features, and your access profile
           is 99% reads, MyISAM will be much faster.
        \_ http://dev.mysql.com/doc/refman/4.1/en/innodb-overview.html
           I think the major items are:
           - transaction (commit/rollback)
           - no REPAIR TABLE needed
           - row level vs. table-level locking
           - foreign keys
2025/05/25 [General] UID:1000 Activity:popular
5/25    

You may also be interested in these entries...
2010/12/11-2011/2/19 [Computer/SW/Languages/Perl] UID:53984 Activity:nil
12/11   Anyone have experience with Perl PDF::API2 or PDF::API3?  Can you
        point me to a good tutorial for creating a simple document (a small
        table of 2-3 rows and a single image)?
	...
2010/7/21-8/9 [Computer/SW/OS/FreeBSD] UID:53890 Activity:nil
7/21    Can I just use ifconfig to expand my netmask on a FreeBSD box?
        Are there any gotchas here? Linux forces me to restart my network
        to expand my netmask.
        \_ yes... and no, you don't have to restart your network on linux either
           \_ Rebooting is the Ubootntoo way!
              \_ Oooboot'n'tootin!
	...
Cache (1491 bytes)
dev.mysql.com/doc/refman/4.1/en/innodb-overview.html
Table of Contents 151 InnoDB Overview InnoDB provides MySQL with a transaction-safe (ACID compliant) storage engine that has commit, rollback, and crash recovery capabilities. InnoDB does locking on the row level and also provides an Oracle-style consistent non-locking read in SELECT statements. These features increase multi-user concurrency and performance. There is no need for lock escalation in InnoDB because row-level locks fit in very little space. You can freely mix InnoDB tables with tables from other MySQL storage engines, even within the same statement. InnoDB has been designed for maximum performance when processing large data volumes. Its CPU efficiency is probably not matched by any other disk-based relational database engine. Fully integrated with MySQL Server, the InnoDB storage engine maintains its own buffer pool for caching data and indexes in main memory. InnoDB stores its tables and indexes in a tablespace, which may consist of several files (or raw disk partitions). This is different from, for example, MyISAM tables where each table is stored using separate files. InnoDB tables can be of any size even on operating systems where file size is limited to 2GB. InnoDB is used in production at numerous large database sites requiring high performance. stores over 1TB of data in InnoDB, and another site handles an average load of 800 inserts/updates per second in InnoDB. InnoDB is published under the same GNU GPL License Version 2 (of June 1991) as MySQL.