Wow, I don't think we've met, then, because I bang on about this all the time. Entirely too much, I'm sure.
I've given a couple of relevant presentations: *http://www.sdruby.org/podcast/120http://www.sdruby.org/podcast/55*Briefly, Postgres is better *in every possible way* than MySQL. Meaning, for any given feature, Postgres is at least as good as MySQL and usually significantly better. In my experience, Postgres is more reliable. It is faster at complex queries. It has many features that are useful for solving tricky optimization problems, including but not limited to: - functional and partial indexes (about which I gave a talk recently) - stored procedures and triggers in any of maybe 20 different languages, including Ruby, Perl, Python and R - Common Table Expressions (which make your SQL much easier to read and write, and allow you to write Turing-complete queries for such things as graph search) - native support for a key-value store (hstore) and JSON as a field type, including with index-accelerated searches for keys and values — meaning Postgres can do just about anything a "document database" can do - advanced indexing features (GIST, PS-GIST and GIN) - the ability to define your own types and operations, and a really great built-in type zoo, including such things as UUIDs, URLs and IP addresses - foreign data access, so you can hit up other databases and data sources directly from your database - a whole bunch of plugins that can give you advanced features and new data types. The most notable is PostGIS, which is about the best way around of doing geographical searches (you could write something like Google Maps using that as the search engine). If MySQL was the only "relation" database available, it would be a wonderful technology. But in fact, other than "I already have lots of MySQL dependent code", there is literally *no* good reason to choose MySQL over Postgres. On Friday, November 21, 2014 6:47:28 PM UTC-8, Chris Schulte wrote: > > Do you have a similar link explaining why Postgres is superior to MySQL? I > know Postgres has all the momentum now in the developer community, but I > can't seem to find any extremely compelling reason why it's held in such > high regard over MySQL (other than the whole evil corporate Oracle owns > MySQL thing). > > Most of the research I've done comes to the conclusion that they're > basically the same, so if you have 10+ years of experience with one then > just stick with it. But that doesn't explain why every developer I meet > turns his/her nose up at the mere suggestion of using MySQL. > > So if you've got some good links I'd appreciate it if you could pass them > along and convince me otherwise. I just haven't heard any reason yet that's > convinced me to make the switch. > -- -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby --- You received this message because you are subscribed to the Google Groups "SD Ruby" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
