RE: [PHP] MySQL vs. Postgresql

Would MySQL be a reasonable database to use for an image database where the images themselves were actually stored in the database? I am talking about ....jpegs, gifs stored in binary format in the SQL database, possibly 10 or 20,000 images. Okay, so the number of records myth was just proven wrong, but how about database SIZE and performance? Gigabytes upon gigabytes? (yes I realize I'm going to have to have gigantic-monster-enormously endowed server) Thanks Dan -----Original Message----- From: Sander Pilon [mailto:sander@3dnews.net] Sent: Wednesday, October 11, 2000 11:10 AM To: Glover George; php-general@lists.php.net Subject: RE: [PHP] MySQL vs. Postgresql > I'm sorta feeling like I missed the boat. Almost everyone I see using php > is using MySQL. Why? Does it have any advantages over > Postgresql? It was > my understanding that Postgresql was a more robust package? Am I wrong. > > Feel free to throw some comments my way. > > > Laterz. > > dime Postgres has a lot of limitations too, MySQL is in general faster and more user-friendly. Personally I decided not to use Postgres beacause it was 1) slower and 2) didnt easily support large character fields. (100Kb+) (Postgres has a horrible way of dealing with BLOB/CLOB's) A reasonably new database called 'Frontbase' (www.frontbase.com) will probably replace MySQL in my setup in a few months, when the frontbase team addresses some issues with documentation and tools. Frontbase is going to woop some postgres and mysql ass I think :) And the myth that MySQL crashes after 500K records is absurd. I have millions of records in MySQL, and it doesn't crash. And small site => mysql, large site => postgres is such a simplistic statement too. Sander -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net For additional commands, e-mail: php-general-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net