RE: [PHP4BETA] one final question for today :)

This is an age old debate. MySQL is faster on non-huge data. It doesn't support transactions or foreign keys (though I don't believe in foreign keys...). It has limited stored procedures, but I really don't think they count. Again I don't totally believe in stored procedures though... I think that's what code is for, not databases :). Regardless, it comes down to what you need in your SQL server. If you need foreign keys, transactions or stored procedures, or have a HUGE dataset (millions of records, a few unofficial benchmarks I've seen has shown PGSQL handles those much better), use PG. If you need blistering speed for simple queries on small to large size datasets, use MySQL. The key is picking the right tool for your job. And this probably isn't the right place to ask but that's okay :) ---------------------------------------------- Cristopher Daniluk cris@dsnet.net Technical Specialist MicroStrategy, Inc ---------------------------------------------- -----Original Message----- From: seth banks [mailto:seth@subimage.com] Sent: Thursday, February 03, 2000 4:54 PM To: php4beta@lists.php.net Subject: [PHP4BETA] one final question for today :) ok, i know i've been kind of annoying today, but this is the last question i promise! mySql or PostgreSql? ... i have heard mySql is very fast, yet doesn't support transactions, stored procedures, or foreign keys...is this true? is the speed great enough to not have to use stored procedures? i am coming from an sql-server7/access background here...where sp's are _much_ faster in ss7 than plain sql queries. does mySql support constraints? (should i be asking these questions somewhere else?) // seth - subimage.com -- PHP 4.0 Beta Mailing List <http://www.php.net/version4/> To unsubscribe, e-mail: php4beta-unsubscribe@lists.php.net For additional commands, e-mail: php4beta-help@lists.php.net To contact the list administrators, e-mail: php4beta-admin@lists.php.net