<PROVOCATIVE RANT> MySQL doesn't provide "native" support for transactions but is dependent on the Berkeley or InnoDB table types.
Does MySQL really provide TRUE row level locking? That's the claim but is it valid? The InnoDB web site seems to be more accurate by explaining that locking is a next-key value locking mechanism that is indexed based. Here's what the InnoDB manual says, "InnoDB does the row level locking so that when it searches or scans an index of a table, it sets shared or exclusive locks on the index records in encounters. Thus the row level locks are more precisely called index record locks." I developed some of my own benchmark tests which intentionally stress transactions in an artificial manner. The results were that MySQL with InnoDB didn't even come close to the performance of Oracle. Maybe my tests weren't very realistic and maybe a real world application won't encounter locking problems but I wouldn't just assume that InnoDB will scale like Oracle or meet the needs of your application. You've got to test it! "Open-source database providers readily admit that their databases are not yet geared toward powering high-end enterprise systems, such as ERP and CRM applications." From an Infoworld article about open-source databases entitled "Finding an opening..." http://www.infoworld.com/articles/pl/xml/02/09/23/020923pldatabses.xml One more thing to rant on... Regarding benchmark test... http://www.mysql.com/doc/en/MySQL-PostgreSQL_bench_marks.html Quoting from this page: "We know of two benchmark tests that claim that PostgreSQL performs better than MySQL Server. These both where multi-user tests, a test that we here at MySQL AB haven't had time to write and include in the benchmark suite, mainly because it's a big task to do this in a manner that is fair to all databases." It's "funny" how MySQL AB just hasn't had time to write a multi-user benchmark. Based on the age of the link they haven't had time for a long time now. Yet they say benchmarking is important? Give me a break! What we desperately need are some TPC benchmarks for the open-source databases. Benchmarks which are independenttly audited and verified. </PROVOCATIVE RANT> -----Original Message----- From: Josh Trutwin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, September 25, 2002 10:03 AM To: [EMAIL PROTECTED] Subject: Re: MyISAM or InnoDB > We are moving a databse over from Oracle to MySQL 4.0.3 and I was > wondering if I should use MyISAM or InnoDb. The databse currently has > 800-900 updates and inserts done to it in a day along with about 1000 > selects. Would I run in to any table locking problems with MyISAM? If you want to support transactions and/or foriegn key constraints then you have to go InnoDB. As for locking problems, I would guess not, but I'll leave that to more experienced list members. Josh > Thanks in advance. --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
