You guys are just resisting being thorough and correct.  Both MySQL and
Postgres are RBDM's.  It's usually easy to switch them out for most of the
frameworks used in the tests.  However usually one or the other has
preference and more tools for it.

In Django, if you don't have legacy data, South migration smoothness alone
makes the switch to Postgres make better sense.  In terms of support for
fast DB access, all of the tools are better for Postgres.  I don't buy this
we-tested-out-of-the-box argument when you're ending up with the clearly
less preferred RBDM for Django.  Get on the IRC.  Ask which RBDM to use.  I
bet there's a bot command that says, "friends don't let friends use MySQL."


On Fri, Mar 29, 2013 at 9:59 AM, Tarek Ziade <notifications@github.com>wrote:

> In django/hello/hello/settings.py:
>
> > @@ -9,17 +9,42 @@
> >
> >  MANAGERS = ADMINS
> >
> > +
> > +#  WTF?  Use Postgres.  It's SQL.  It has better support under Django
>
> what's the point ? if you are going to compare with other apps that are
> using mysql, it makes no sense to have the django app using postgres...
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/TechEmpower/FrameworkBenchmarks/pull/20/files#r3586650>
> .
>