Re: Data banks comparisons

<comment opinion=yes flames=no> Personally, I wouldn't use MYSQL for an enterprise solution. It is really made for quick data retrieval, and doesn't support important things such as transactions, which are essential in any application where data integrity is important. Go for at least PostgreSQL if it's only a small solution, that is it will only be under fairly light load. 200 users should be fine, but here we use Sybase, so I don't know how PG stands up under strain. </comment> ----- Original Message ----- From: Zehnder Patrick <patrick_zehnder@gmx.ch> To: PHP-DB LIST <php-db@lists.php.net> Sent: Thursday, September 07, 2000 10:17 PM Subject: [PHP-DB] Data banks comparisons > Hi, > > I compare some data banks solutions for an enterprise. They need a > solution, which is: > - quick > - easy and quick for programming > - easy to use > - safe > - support 200 users at the same time > > Now, I study an Linux, Apache, PHP and MySQL solution. Can this be a > solution for this enterprise? > > In the documentation of MySQL I found a lot of benchmark-information. > But I found not the limits for a one-server-solution. What are the > limits for this "solution". > > Sorry about my English. > > Thanks for answers! > > Patrick Zehnder (Switzerland) > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, e-mail: php-db-unsubscribe@lists.php.net > For additional commands, e-mail: php-db-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net > >