Adam, MySQL has transactions now. I believe the component name you need is innodb.
One thing people might want to look at is SAPDB. It's been used in enterprise applications for some time. It's also Open Source. I believe the last few wrinkles have been worked out so that it compiles on Linux/390. SAP just recently licensed the development to MySQL AB, and they'll be re-releasing it under the name MaxDB. Mark Post -----Original Message----- From: Adam Thornton [mailto:[EMAIL PROTECTED] Sent: Friday, August 22, 2003 10:08 AM To: [EMAIL PROTECTED] Subject: Re: MySql On Fri, 2003-08-22 at 08:02, David Goodenough wrote: > for anything serious use Postgresql I would tend to second this (presuming you want to save money by not going with a commercial solution, although I've heard from people in the x86 world that PostgreSQL is at least as fast as Oracle). MySQL--at least, last I looked--didn't really promise transactional integrity. It *is* however, blindingly fast. If what you need is to move a lot of data around, and the information itself isn't so criticial--you could ask the user to hit refresh or something (a la Slashdot), MySQL is very good. If you need to move a bunch of bits with real value and the transaction must occur exactly once, then PostgreSQL would be my choice. Adam
