Well I would try and play with the two. But on the server that hosts us, they have MySQL, thats why I was looking to learn that one.
Thank you for all the information, I acctuly was going to ask if there was an online tutorial to read. But I forgot so thank you guys for throwing that in there to. The reason why I want to use SQL is I want to do away with my webserver. I really love my webserver but it is so limited. Mainly cause it can only do HTTP 1.0, and that won't let me use perl. So I figured moving everything over to SQL, I could still use the old webserver to give some of the information it was. But I could really expand my logged in section to include a little more... So thank you guys for all you help. ----- Original Message ----- From: "Jason Gauthier" <[EMAIL PROTECTED]> To: "Chad Simmons" <[EMAIL PROTECTED]> Cc: <[email protected]> Sent: Thursday, March 11, 2004 10:27 AM Subject: RE: Kind of off topic > 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 > > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom
