On Fri, 2006-03-11 at 13:17 +0000, elake wrote: > Thanks. Thats what I thought. I think that we are going to put up a > site that is all from a WYSIWYG and in the background I am going to > work on a Django powered site. Would you recommend Postgres over MySQL > or the other way around?
I think that is a wise choice. You could use something static or do a Drupal install, and then you won't be trying to learn Django under deadline. If I can't get a client to bite for a custom CMS in Django, Drupal is the off-the-shelf cheap solution I recommend because it is at least well documented, cleanly coded ( though in PHP ) and easy to install and maintain. Sometimes a client is determined to muck around with the CMS themselves and I can trust them more with Drupal than with Django code. ( It's dead easy to break a django site if you don't know what you're doing! ) Django makes web dev much much faster, but does not really make it *easier* for a beginner, in that you do have to understand and wrap your head around a fair bit of coding to get it going. For an experienced coder on the other hand, it makes building a complex CMS far easier. For what you are doing I don't think it will matter which RDBMS you use. I personally use MySQL because I never do anything complicated with a database ( where Postgres would shine ) and MySQL is IMHO better documented for the beginner and more widely available on cheap hosting. Django will talk to both just fine so go with whatever looks easiest to get up and running. You may even want to use SQLite to lower hosting costs. Hope that is useful, Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
