101 Reasons Why PostgreSQL is a better fit for Rails than MySQL

Newsletter Subscription | Glossary | Contact Us

Home > All Categories > PostgreSQL > Announcements > 101 Reasons Why PostgreSQL is a better fit for Rails than MySQL

101 Reasons Why PostgreSQL is a better fit for Rails than MySQL

Authored by: Thomas Darwin
Viewed: 146 times so far

1 - Indexing Support

MySQL cannot utilize more than one index per query. I believe this is worth repeating: MySQL CANNOT UTILIZE MORE THAN ONE INDEX PER QUERY. Wait till your tables get large enough and this will surely hit you. OTOH PostgreSQL can use multiple indices per query which come real handy.

2 - Full Text Indexing Support

MySQL can do full text indexing on MyISAM tables only, those working with InnoDB tables are out if luck. PostgreSQL has very advanced full text indexing capabilities wich enable you to control the tiniest details down to the stemming strategy.

3 - Asynchronous Interface

MySQL drivers are very unfriendly to the Ruby interpreter. Once a command is issued they take over until they come back with results. PostgreSQL sports a completely asynchronous interface where you can send queries to the database and then tend to other matters while the query is being processed by the server. The good news is that an Async ActiveRecord adapter for MySQL is being developed right now, as part of the rapidly growing NeverBlock library.

Read more ...

Author : Muhammed Ali
Source : http://oldmoe.blogspot.com

Click Here to View all the questions in Announcements category.

File Attachments