MySQL is like MS Access. It's an OK database, but it doesn't scale nearly as far as PostgreSQL. MySQL doesn't support many features such as transactions or views. MySQL designates simplicity over functionality.
Having said that.... MySQL is MUCH easier to find information about, especially in the PHP realm, leading me to also believe it is more popular there. MySQL's lacking features may well not matter for this installation. Converting from one to the other isn't the end of the world. My experiences have been limited, but good with both My and Postgres. I 'trust' postgres much more than My, but I can't give a justifiable reason. Perhaps it's just that the (yeah, yeah, save it.) tools used to administer Postgres from a legacy Windows desktop seem much more polished than the tools available for administering MySQL from Legary Windows boxes. Overall, this is a geek version of the "Dodge rules, Ford is crap" argument. Kev. ----- Original Message ----- From: "Andrew J. Kopciuch" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 15, 2002 2:48 PM Subject: Re: (clug-talk) MySQL and PHP books and resources recommendation. > On Tuesday 15 October 2002 14:38, J. Rafael Sánchez wrote: > > I actually prefer to use MySQL as my database engine instead of PostGres > > at this time. Thanks for the info though! > > > > Any particular reason why? > >
