I recommend if you do transactions a lot, stick to Postgresql by all means. MySQL isn't transactional database, to test what I mean, create a InnoDB database with a very simple InnoDB table (two columns would be fine), than do 1000 inserts in transactions; note the time and you will find that InnoDB is very very slow on insert, plus transactions death locks are very frequent.
On Monday, November 5, 2012 7:50:56 AM UTC+5, martharotter wrote: > > I was advised recently to port my startup's Django databases from postgres > to mysql for two reasons: > > 1) RDS on Amazon makes it your life much easier > 2) When I need to scale my web app and have to hire people to help me, it > will be much easier to find solid mysql people than postgres people. > > Any thoughts on these? Are they legitimate concerns? It's always a pain to > migrate, but I guess if it's worth doing I'd rather do that now when it > makes less of an impact. > > Thanks in advance for your help! > --Martha > http://woop.ie > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/dJ8jP6DRylgJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
