Hacker News Reader

I could be wrong, but I feel the same could be said for rails (until very recently). It seemed to me that rail's primary target (and maybe ruby at large) is mysql and postgres support was just an afterthought (until the latest 2.2.2 release for rails)

the only places that I don't feel treat mysql as the main premiere db is python and java

in mysql's defense, they have come a long way. they finally added stuff like stored procedures and triggers

View on HN

In what way do you feel like rails support for postgresql is an afterthought?

I've noticed some books / documentation assume mysql, but that's usually limited to the "and now setup your database" section.

I've been using rails + postgresql for a long time now (almost 2 years in production) and I can't think of a single problem that was due to not using mysql. Of course, I don't use every plugin or feature, so there may be something out there...

the last one I remember are postgres specific bugs involving postgres datatypes.

my memory could be fuzzy but I feel that this would generally occur after a fresh rails release (2.2.2 is the exception)

well I am in the midst of migrating my rails app to postgres now - hopefully what I feel and reality don't match

Reply on news.ycombinator.com