> One of the big advantages of MySQL is ease of use and a choice when it comes > to how you store data. For example: if you need fast reads and less updates, > make your table MyISAM (you can even compress it making it smaller and > faster!). If you need high availability of your data, you can go MySQL > Cluster. Need a data to /dev/null, use the blackhole engine! ;)
This probably explains shoot outs I had read last year that claimed MySQL was more appropriate in a case where your database needs are simpler, but you expect to have the server doing a *lot* of small hits ( say a high traffic forum ), whereas PostGres shone for more sophisticated transaction support ( say an ordering system with payment gateway). My data may well be out of date on this, however. As with many things, the two keep getting closer. IMHO, if you are doing simple stuff with the DB ( say cms things ) and you are relatively new to it all, MySQL documentation seems to be more accessible to newbies and more prevalent on the internet. It's worth thinking that what might be *best for you* is not necessarily *the best product*. Ease of use and documentation are more important for db-lite beginner cases, less so for complicated e-commerce transactions where your going to be making damn sure you know what you're doing. Iain --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
