Re: Web application?

Martín Marqués pressed the little lettered thingies in this order... > > If you are going to have concurrent users loading and reading, then MySQL > is surely not the best choice. > > Saludos.... ;-) Do you mind qualifying this statement? I've managed MySQL servers with relatively weak hardware that handled 350,000+ database queries per hour without flaw. As Rasmus stated earlier in this thread, "You need to concentrate on making an efficient schema and making sure you eliminate table-scans, etc." If you can't do that, no database server will help you. If you can - and you don't need transactions or sub-selects (transactions are now supported with the latest version, but you have to use a non-native table type and sub-selects are coming soon) - then MySQL is probably THE choice for a busy server. Have a look at the benchmarks on their site if you don't agree. Christopher Ostmo a.k.a. tech@AppIdeas.com AppIdeas.com Innovative Application Ideas Meeting cutting edge dynamic web site needs since the dawn of Internet time (1995) For a good time, http://www.AppIdeas.com/