I''ve tried searching on the internet but to no avail. What are the advantages of each of the databases? I''m going to be building a web application, which would be best for that? Thanks in advance. _______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
A couple of cursory thoughts about the two: Mysql - Typically better supported by hosting companies - Sounds like it''s a bit better supported by ruby libraries, or at least, more easy to get working by default - Is certainly used by large web applications (eg Yahoo) - Has plenty of good client side tools available Postgres - Some anecdotal evidence indicates that it''s less prone to table corruption problems under heavy load. - Has support for more advanced functionality, including: - More rigid constraints on tables (eg foreign keys and other constraints) - Views - I found some simple tasks to be a little harder to do in postgres (such as auto number fields), as it''s functionality is more generic and more powerful In summary, if you don''t have any particular preference at the moment, I''d probably go with mysql for no other reason that it''s more common. With rails, you shouldn''t have too much hassle changing later if you decide that a different database engine better suits your needs. Craig On Sat, 11 Jun 2005 6:02 pm, Oliver Legg wrote:> I''ve tried searching on the internet but to no avail. > > What are the advantages of each of the databases? > > I''m going to be building a web application, which would be best for > that? > > Thanks in advance.-- Craig Ambrose Web Elements http://www.portallus.com/people/craigambrose/
On Jun 11, 2005, at 1:18 AM, Craig Ambrose wrote:> A couple of cursory thoughts about the two:Please discontinue this thread. The parent is clearly a troll. Thank you, jeremy
What led you to believe that it is a troll. I just want people''s opinions on what the advantages and disadvantages of the two databases are, if any. How is that in any way troll like? On 11 Jun 2005, at 10:42, Jeremy Kemper wrote:> On Jun 11, 2005, at 1:18 AM, Craig Ambrose wrote: > >> A couple of cursory thoughts about the two: >> > > Please discontinue this thread. The parent is clearly a troll. > > Thank you, > jeremy > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >_______________________________________________ Rails mailing list Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org http://lists.rubyonrails.org/mailman/listinfo/rails
> Please discontinue this thread. The parent is clearly a troll.I''m not so sure... even if it was, I''m curious about the differences too, and I think my history (however brief) indicates I''m not a troll... Ben
On Sat, 2005-06-11 at 11:02 +0100, Oliver Legg wrote:> What led you to believe that it is a troll. I just want people''s > opinions on what the advantages and disadvantages of the two > databases are, if any.I prefer PostgreSQL... but I take advantage of its advanced features. (I can program stored procedures/triggers in Ruby, Python, Perl, and PHP). ..but it''s best you decide for yourself. MySQL Gotchas: http://sql-info.de/mysql/gotchas.html PostgreSQL Gotchas: http://sql-info.de/postgresql/ -- /****************************************************** * Robby Russell, Owner.Developer.Geek * PLANET ARGON, Open Source Solutions & Web Hosting * Portland, Oregon | p: 503.351.4730 | f: 815.642.4068 * www.planetargon.com | www.robbyonrails.com *******************************************************/
On Sat, 2005-06-11 at 10:35 -0700, Robby Russell wrote:> On Sat, 2005-06-11 at 11:02 +0100, Oliver Legg wrote: > > What led you to believe that it is a troll. I just want people''s > > opinions on what the advantages and disadvantages of the two > > databases are, if any. > > I prefer PostgreSQL... but I take advantage of its advanced features. (I > can program stored procedures/triggers in Ruby, Python, Perl, and PHP). > > ..but it''s best you decide for yourself. > > MySQL Gotchas: http://sql-info.de/mysql/gotchas.html > > PostgreSQL Gotchas: http://sql-info.de/postgresql/Might I also show some helpful numbers: Google search for: http://www.google.com/search?q=%22mysql+sucks%22 3,750 for "mysql sucks" http://www.google.com/search?q=%22postgresql+sucks%22 18 for "postgresql sucks" So, there you have it. ;-) </sarcasm> -Robby -- /****************************************************** * Robby Russell, Owner.Developer.Geek * PLANET ARGON, Open Source Solutions & Web Hosting * Portland, Oregon | p: 503.351.4730 | f: 815.642.4068 * www.planetargon.com | www.robbyonrails.com *******************************************************/
On Jun 11, 2005, at 3:02 AM, Oliver Legg wrote:> What led you to believe that it is a troll. I just want people''s > opinions on what the advantages and disadvantages of the two > databases are, if any. > > How is that in any way troll like?Because it asks in a vague way for an answer to an unanswered, contentious question. Your intent was not to troll, but the question qualifies nonetheless. "MySQL versus PostgreSQL" googles 320000 hits. There are extensive resources for both RDBMS as well as plenty of debate over their inherent worthiness and well-suitedness to web applications. It mostly boils down to PostgreSQLers bashing on MySQL''s feebleness and MySQLers snubbing their nose at them. Internet invective is a poor decision maker. For a pragmatic answer, work with each to discover their strengths and weaknesses. Explore other options such as the lesser-known SQLite or Firebird. Then you''ll have a broad set of tools and know when to use them. Best, jeremy
On 6/11/05, Robby Russell <robby-/Lcn8Y7Ot69QmPsQ1CNsNQ@public.gmane.org> wrote:> Might I also show some helpful numbers: > > Google search for: > > http://www.google.com/search?q=%22mysql+sucks%22 > > 3,750 for "mysql sucks" > > http://www.google.com/search?q=%22postgresql+sucks%22 > > 18 for "postgresql sucks" > > So, there you have it. ;-)This doesn''t prove mysql sucks more... in fact, these numbers *could* indicate that mysql and postgresql suck equally, it''s just that mysql has that many more users (and the larger number of users could be explained by marketing and have nothing to do with technical merit). It could also mean that Postgresql users are more sophisticated and would say "I dislike postgresql" instead of "postgresql sucks", which wouldn''t show up in your statistics. But I prefer postgresql anyway ;) -- Urban Artography http://artography.ath.cx
There''s a vast deal of documentation on the pros/cons of each system, often in direct comparison, on the internet. Even the PostgreSQL and MySQL sites have specific answers to this question. I''ve not used MySQL except for Rails tests, but I have used PostgreSQL extensively. PGSQL is outstanding, reliable, pretty fast, very SQL standard compliant, but fairly low-level in terms of management tools. I use their command line tools and interface. On 6/11/05, Rob Park <rbpark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> On 6/11/05, Robby Russell <robby-/Lcn8Y7Ot69QmPsQ1CNsNQ@public.gmane.org> wrote: > > Might I also show some helpful numbers: > > > > Google search for: > > > > http://www.google.com/search?q=%22mysql+sucks%22 > > > > 3,750 for "mysql sucks" > > > > http://www.google.com/search?q=%22postgresql+sucks%22 > > > > 18 for "postgresql sucks" > > > > So, there you have it. ;-) > > This doesn''t prove mysql sucks more... in fact, these numbers *could* > indicate that mysql and postgresql suck equally, it''s just that mysql > has that many more users (and the larger number of users could be > explained by marketing and have nothing to do with technical merit). > > It could also mean that Postgresql users are more sophisticated and > would say "I dislike postgresql" instead of "postgresql sucks", which > wouldn''t show up in your statistics. > > But I prefer postgresql anyway ;) > > -- > Urban Artography > http://artography.ath.cx > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
> I''m not so sure... even if it was, I''m curious about the differences > too, and I think my history (however brief) indicates I''m not a troll...Hopefully we can discuss it without starting a flamewar :-) After all these are just tools, and the question is, what is the right tool for the right job... I use PostgreSQL when: - I need db consistency, even over unexpected power shutdowns or crashes - I need (sophisticated) stored procedures and rules (you can program them in several languages, even in ruby) - I need rock solid transactions - I need schemas - in general, when my db design will be large and I expect performance problems with active record, postgresql is a perfect choice (due to its good stored procedures/views support I''m able to take care of some stuff on db level instead of in active record). I use MySQL when: - I need raw speed and don''t need transactions - I have big flat tables, lot''s of retrieving, not so much updating/creating - I have someone else (with less db experience) administer the database (mysql has more admin tools, php scripts etc. available to make it easy, although now with rails and scaffolding, that argument is getting obsolete :-) ) - I have a simple straightforward db design. typical application I would do with postgresql: - order/tracking/production system (ERP, transactions, robustness) typical application I would do with mysql: - forum, wiki, news site (lots of reads for many concurrent users, low amount of (concurrent) updates/writes) But it is perfectly possible to build an ERP system in mysql and a forum in postgresql of course. Best regards, Bas
On Jun 11, 2005, at 10:41 AM, Robby Russell wrote:> Might I also show some helpful numbers: > > Google search for: > > 3,750 for "mysql sucks"7,760 for "mysql rules"> 18 for "postgresql sucks"345 for "postgresql rules"> So, there you have it. ;-)MySQL rules:suck ratio: 2.069 PostgreSQL: 19.167 So Postgres is roughly 9 times as good.> -Robby-Dane
Oliver Legg wrote:> What led you to believe that it is a troll. I just want people''s > opinions on what the advantages and disadvantages of the two > databases are, if any. > > How is that in any way troll like?Well, OK, if this is not a troll then, 1. If you don''t know what database is better, choose MySQL because it is better supported by ISPs. 2. See #1. If you later find out that you prefer or need PostgreSQL''s flexibility and features, then you can just migrate to PostgreSQL. - Adam
On Sat, 11 Jun 2005, Ben Bleything wrote:> I''m not so sure... even if it was, I''m curious about the differences > too, and I think my history (however brief) indicates I''m not a troll...I suggest studying C.J. Date''s _An Introduction to Database Systems_. PostgreSQL is a reasonably decent implementation of an RDBMS. MySQL is not. This might not make any sense to you until you find out what an RDBMS is, and how it can help you, and even then you may not care; many people don''t. cjs -- Curt Sampson <cjs-gHs2Wiolu3leoWH0uzbU5w@public.gmane.org> +81 90 7737 2974 http://www.NetBSD.org Make up enjoying your city life...produced by BIC CAMERA
On 12-jun-2005, at 4:34, Bas van Klinkenberg wrote:>> I''m not so sure... even if it was, I''m curious about the differences >> too, and I think my history (however brief) indicates I''m not a >> troll... >> > > Hopefully we can discuss it without starting a flamewar :-) After > all these are just tools, and the question is, what is the right > tool for the right job... > > I use PostgreSQL when: > > I use MySQL when: > > typical application I would do with postgresql: > - order/tracking/production system (ERP, transactions, robustness) > > typical application I would do with mysql: > - forum, wiki, news site (lots of reads for many concurrent users, > low amount of (concurrent) updates/writes)I second this opinion. However, there is a number of very clever things you can do using PostgreSQL that you might find useful. For example, you can have "shadowing" using views - so that you can expose your authentication table to a forum engine that was written by someone else and integrate the two systems on database level. I started with MySQL, then switched to PostgreSQL - I would say, if your host supports Postgres - go for it. If not - stick with MySQL. It is also reasonably easy to migrate from MySQL to Pg along the way when you need it (provided that you don''t use MySQL intrinsics such as "set" fields etc.). As long as you stick to standard SQL and standard types you should be on the safe side to switch from one to another in a few days. Migration from Pg to MySQL on the other hand is virtually impossible. -- Julian "Julik" Tarkhanov