On Monday 27 January 2003 02:53 pm, Jopoy C. Solano wrote: > Thanks! It confirms my first choice :)
i use postgres with php. we've used mysql too, but that was for old projects. we went with postgres because at the time mysql didn't have sub-selects or transactions. i have not been keeping track of mysql development though. i know that transactions were available some time ago if you used innodb, i think. and i think they were working on sub-selects and that might be working by now. [warning, as i said above, i have not actually been paying much attention to mysql, so my impressions of progress above may be wrong, they're based on reading about, not actually using, those features]. of course, while mysql was playing catch-up, we got used to postgres, liked it, and we've not needed to test mysql. i'd say, both are good enough as database engines, and you might need to decide which one to use based on some other metric (flip a coin, which syntax you like, popularity with hosting services [including the version and features you need, because some hosting services might still be using old versions], front end software available (e.g., pgaccess), platforms supported (they're probably pretty equal), other weird options, e.g., if one allows you to completely turn off transactions and you need speed more than you need transaction safety, then that might be a decision point for you). tiger -- Gerald Timothy Quimpo tiger*quimpo*org gquimpo*sni-inc.com tiger*sni*ph Public Key: "gpg --keyserver pgp.mit.edu --recv-keys 672F4C78" my name is Inigo Montoya. You killed my father. Prepare to die. _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
