My work (MOBI
) switched from mysql to postgresql about 10 months ago. So far we are loving it. Seems much more durable than mysql. Plus the hstore, array, and boolean column types are a great feature if you have a need for them. Also setting up streaming replication is a walk in the park compared to mysql. I do agree there is some bit of a learning curve if coming from mysql (users in mysql are instead called "roles" and string comparisons are case insensitive in postgesql). The documentation is also very fleshed out.
Also, shame on you. You should always try to replicate production locally as much as possible. ;) (yes, we do all run postgresql locally for development)
On Fri, Aug 17, 2012 at 4:49 PM, Jim Bartek <[address removed]>
a few questions from a noob. Also last meetup was great, thanks.
Are people using postgres much, or just sticking to mysql? And if using postgres in production, are you using postgres in development on your local machine (as recommended)? I am looking for justification to use it because it is more painful to setup, etc.
When deploying to Heroku cedar stack, is best practice to precompile locally, or setup to let heroku do the work when you push it? I understand that realtime is not a good idea.
here is the page i have been looking at: https://devcenter.heroku.com/articles/rails3x-asset-pipeline-cedar/. Also is Heroku still the preferred deployment platform to get small projects working quickly?
Thanks in advance.
Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
This message was sent by Jim Bartek ([address removed]) from indy.rb - The Indianapolis Ruby Brigade.
To learn more about Jim Bartek, visit his/her member profile
Set my mailing list to email me As they are sent | In one daily email | Don't send me mailing list messages
Meetup, PO Box 4668 #37895 New York, New York[masked] | [address removed]