On Tue, 2006-04-18 at 17:34 +0200, Alder G. wrote:
and this: http://wrath.rubyonrails.org/pipermail/rails/2006-April/030188.html
WRT migrations, look here:
I’m not so much bothered by the issues with migrations - which I’m
unlikely to use - but searching this list’s archives gave the
impression that PostgreSQL is less supported in Rails, backwards
compatibility to it is deemed less crucial, and in any case - people
using it in Rails tend to have more issues with it than with MySQL,
which for the Rails framework seems to be the database most supported.
It appears that you are making judgments based upon initial reactions to
changes that occurred and I can assure you that migrations works
perfectly with postgresql and I’m working towards unit tests but as had
been stated by another on this thread, they aren’t an issue with
Recognize that this list has people with all varying levels of knowledge
of ruby/rails - in fact, most are probably less knowledgeable and thus
you get questions like the ones you listed but often, they are not
indicative of any real problems.
Since you seem inclined to go with MySQL, go for it. Each different
database has its strengths and weaknesses but in case of Rails, both
PostgreSQL and MySQL are fully usable.
As for being bothered by issues with migrations…you should be if it
were true. Migrations abstracts the actual database used so you could
easily move between different db’s and test them out for yourself if you
chose. At this point, knowing what I have learned in the last 3 months,
I wouldn’t develop Rails without migrations and svn.