On Feb 21, 2007, at 15:52, Sundial Services wrote:
> > The essential differences to consider are (1) transactional support, > and (2) data-types and SQL support. Both systems can be expected to > deliver comparable performance under ordinary loads. Newsflash.. MySQL has had transactional support since 3.23.34 with InnoDB engine.. > On Feb 21, 9:36 am, "Grupo Django" <[EMAIL PROTECTED]> wrote: >> Hello, I want to know which of these two databases are prefered by >> django. I can choose and I'd like to know if there is some >> differences >> in performance or integration (like foreign keys). >> If someone knows a comparative between both of them it would be good, >> not only about django integration but about everything. Since I'm biased (I work for MySQL) I can only tell you: The one you most comfortable with, you go for. On a more subjective note. I like MySQL more over PostgreSQL because it gives you a choice going transactional or not per table (I consider that a BIG feature). MySQL has native replication, is easier to setup and tune, maintain and has native GUI tools. (Has also native commercial support if needed :PP) On the other hand, there are features you might maybe like better in PostgreSQL, like GIS support. But having more 'features' doesn't mean you will need them. I worked with PostgreSQL as well, and the stored procedures back then written in Python were cool. :) For Django however, it shouldn't matter what you choose. Cheers, Geert -- Geert Vanderkelen http://some-abstract-type.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
