I think Ariel's reply is spot-on.  Rails is basically DB agnostic, however I 
think the trend is that PostgreSQL is the more favored backend (except for 
stuff like Wordpress).  We're doing a lot more SQL procedural stuff these days 
with our rails apps (e.g. kicking out JSON from a single query can be literally 
1,000x times faster in cases vs. asking Rails to query a model and format the 
same thing).  I find PostgreSQL a lot easier to admin as well, but to each 
their own.

Good luck!


Phil


> On Mar 14, 2020, at 7:37 AM, Ariel Juodziukynas <arielj...@gmail.com> wrote:
> 
> Usually ActiveRecord takes care of most of the differences, and postresql has 
> a lot of similarities with mysql. I guess it would be a different call if you 
> ask about learning a completely different db engine like mongo or graphql, 
> but learning postgresql shouldn't take too much time knowing MySQL, at least 
> to be proficient. I even have a project that I used sqlite to prototype and 
> postresql when deploying it to heroku for tests and I had to do nothing to 
> make it work on both databases thanks to AR.
> 
> Also, heroku prefers postrgres for example and heroku is really popular for 
> rails hosting.
> 
> El sáb., 14 mar. 2020 a las 10:58, Rob Jonson (<rob.jon...@gmail.com 
> <mailto:rob.jon...@gmail.com>>) escribió:
> Hi Folks,
> 
> I have been using Mysql for forever, and broadly it works fine for me, with 
> two complaints
> 1) occasional issues with mismatches in encoding/collation on strings
> 2) hours lost on every mac upgrade trying to get mysql working properly again
> 
> I know that people are generally favouring postgresql these days, I'm 
> wondering if anyone can comment on whether it's worth putting in the effort 
> to learn a new db?
> 
> all the best
> 
> Rob
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonrails-talk+unsubscr...@googlegroups.com 
> <mailto:rubyonrails-talk+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rubyonrails-talk/495925de-561d-4561-bb70-dfe9549219a8%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/rubyonrails-talk/495925de-561d-4561-bb70-dfe9549219a8%40googlegroups.com?utm_medium=email&utm_source=footer>.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to rubyonrails-talk+unsubscr...@googlegroups.com 
> <mailto:rubyonrails-talk+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/rubyonrails-talk/CAPS3bcBqX0Y3R_63yfarpdV%2B0qesh3VGzeTzP2bV0inbGMxoOQ%40mail.gmail.com
>  
> <https://groups.google.com/d/msgid/rubyonrails-talk/CAPS3bcBqX0Y3R_63yfarpdV%2B0qesh3VGzeTzP2bV0inbGMxoOQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to rubyonrails-talk+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-talk/BE54840B-0F95-4AB6-831B-90A3205AD2A6%40gmail.com.

Reply via email to