They also have completely different C APIs. He really should experiment with both to determine which avenue to take.
> > -----Original Message----- > From: Chad Simmons [mailto:[EMAIL PROTECTED] > Sent: Thursday, March 11, 2004 12:16 PM > To: Jason Gauthier > Cc: [email protected] > > > --- Jason Gauthier <[EMAIL PROTECTED]> wrote: > > Please elaborate. > > > > MySQL and Postres perform at generally the same level. > > Robustness is debatable with each project having it's own target. > > Common sense changes person to person. > > > > He should choose the SQL database that fits his needs the best, by > > exploring his options, not taking the opinions of a > postgres enthusiast. > > > > > > I'm not recommending MySQL in this post. I choose the tool best for > > the job I'm doing. He should do the same. > > > > Well MySQL's focus has been on performance first. PostgreSQL > focuses more on > being fully featured. This is not to say that PostgreSQL will > be noticably > slower for most things, or that MySQL is a barebones > featureset. In general I > would say that if one wants to make the most out of an SQL > database (and isn't > running up against serious performance issues) PostgreSQL would be my > recommendation. But that's just my opinion. > > ~Kender > > ===== > -----BEGIN GEEK CODE BLOCK----- > Version 3.1 > GCS/L/C/O d-(+) s++: a-- C+++$>++++ UBLS++++$ > P+++(--)$ L+++>++++ E--- W+>++$ N !o K? w(--) !O > M- !V PS+ PE(++) Y+ PGP->+ t+ 5 X+() R(+) tv+@ > b++(+++) !DI+++ D G(-) e>+++$ h---() r+++ y+++ > ------END GEEK CODE BLOCK------ > > __________________________________ > Do you Yahoo!? > Yahoo! Search - Find what you're looking for faster > http://search.yahoo.com >
