[17:03:40] <foolmark> Hey all, I'm new here. I'm Mark Kennedy from The Motley Fool (fool.com)
[17:05:01] <foolmark> We're a new Django shop and are looking for some input around deciding whether we should continue using MySQL since that's a known entity for us, or if we should run with Postgres since that's the more standard part of the Django stack. Our DBAs are nervous. Any advice?
[17:32:18] <MattBowen> foolmark: I'd be amazed if there weren't a ton of shops running MySQL with django
[17:32:24] <MattBowen> foolmark: I know we did for years at my last job
[17:32:36] <MattBowen> foolmark: that said, Postgres is nicer (IMO)
[17:33:13] <MattBowen> foolmark: have you all switched to django wholesale?
[18:13:13] <foolmark> Hey Matt, sorry I stepped away
[18:13:24] <MattBowen> foolmark: no worries -- that's how IRC works
[18:13:52] <foolmark> We haven't switched wholesale, we've just started a small project that will most likely grow to encompass more of our site(s)
[18:14:07] <foolmark> Right now we're up and running on http://beta.fool.com/
[18:14:47] <foolmark> so, we have been running with MySQL since we already have that in house
[18:15:47] <foolmark> But we've run into some issues with migrations and a few other things that I don't have details on, and folks were thinking that we might be better off running Posgres because it's more common in Django-land
[18:16:07] <foolmark> It sounds like in your experience MySQL is pretty widely deployed too, huh?
[18:18:20] <MattBowen> foolmark: i mean, i never felt like we were alone. I will say that python programmers tend to prefer Postgres
[18:24:22] <foolmark> matt: Thanks, that's good to know.
[18:24:44] <MattBowen> foolmark: that said, I never use South for migrations
[18:24:55] <MattBowen> most of my django work was before it was merged in