Re: Web application?
| From: | Martín Marqués | Date: | Sat, 14 Jul 2001 14:32:10 +0000 |
| Subject: | Re: Web application? | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-57868@lists.php.net to get a copy of this message | ||
On Vie 13 Jul 2001 22:47, Christopher Ostmo wrote:
> 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."
Agree on this totally. You can't blame the DB server for a bad programmers
work (talking about sql programming).
> 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.
I don't know how you can live without thansactions, unless your database
consist's of just one table for inserts.
Anyway, why don't you look at this:
http://www.zend.com/zend/art/databases.php
(I have seen a MySQL server insert 30/2/1999 in a date field, which doesn't
look ver good, just to talk a little about inconsistency).
Saludos... ;-)
--
Cualquiera administra un NT.
Ese es el problema, que cualquiera administre.
-----------------------------------------------------------------
Martin Marques | mmarques@unl.edu.ar
Programador, Administrador | Centro de Telematica
Universidad Nacional
del Litoral
-----------------------------------------------------------------