> > I'm just deciding which DB to use for my projects and I'm not clear with one > > thing... When considering a database for web, is MySQL good enough? I read > > it only supports table locking, which is not very satisfying in such a > > multiuser environment as the internet.. > > PostgreSQL has transactions and locks single records - MySQL locks > whole tables. > I read something like this: "MySQL is more popular because a lot > application is made in MySQL. If you make a new application from the > base - choose PostgreSQL".
See MySQL 4.x. They also have subselects now (HUGE!). As for an understanding of the importance of row locking vs. table locking, it's probably only going to be an issue if you're recieving a large number of hits per second that actually need to lock records. Be sure to read up on the different table types that are available and their features. It would help if we had a better idea of the goal of your application (EG slashdot doesn't need to lock its user records, etc.). Or it wouldn't matter much if you used 4.x. > > Based on your experience, what are pros and cons of MySQL and why most of > > you prefer to use MySQL to PostgreSQL, which is aparently more powerful.. Honestly? MySQL seems to be more actively used, and more actively developed, and has more programs with hooks for it (even though SQL should be truly universal *sigh*). And I just like it. Didn't really need anything PostgreSQL had to offer at the time, and when it comes that I do need things like subselects, I'll just upgrade my version. -Jeff SIG: HUP -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
