> well I have a book on php,apache and mysql so are there? any > differences between mysql and postgreSQL for django > (proforanmce features etc.)
They're becoming closer in terms of their features. A couple observations in my experience: - MySQL tends to be faster and have some nice "my site mostly reads data and doesn't have so much writing" optimizations (mostly through table-types) - the prevaling intarweb "knowledge" says that MySQL is faster under light load, but doesn't scale as well as PostgreSQL (PG) under heavy transactional load (again, load for reading vs. load for writing may be important here). - PG supports much more ANSI SQL. MySQL is coming closer, but it's still missing some things that I reach for regularly. And some of MySQL's table-types don't support all features (such as transactions) though this allows for some of the optimizations mentioned above. Many hosting services have older versions of MySQL which drive me absolutely bonkers for its lack of certain features (views, sub-queries, etc) - I find MySQL easier to install and administer. PG has a much more "enterprisy" feel to it with the management overhead that goes along with it. This may be the reason more hosting services tend to offer MySQL. - MySQL has full-text search (FTS). The most recent release of PG now has finally integrated their plugin FTS into the default deployment which should close this gap. - MySQL used to have the edge for Win32 deployment, but PG now works on NT-based Win32 (Win2k and WinXP...likely Vista too) - both have their own replication/load-balancing schemes that can be used Fortunately, since they're both free, you can download both and take 'em for a test drive to see which you prefer. Django's ORM also abstracts out many of the differences between them, so it's not as significant unless you're reaching into an extra() call to use some server-specific code. Where it matters, I try to test with Django's "big 3"...PG, MySQL, and sqlite just to make sure it works on all three, but for my quick/development tests, I tend to prefer sqlite for its in-memory DB. Just my thoughts on factors. Weigh against what you need and decide accordingly. -tim --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
