walterbyrd wrote: > I know that PostgreSQL is recommended, but why? Are the django > developers assuming a high-traffic, database intensive site.
Not necessarily. Using a separate server, instead of an embedded one, you pay a small setup cost once, and then reap benefits all the time. > Are the django developers assuming that you will not be using shared > hosting? There's lots of PostgreSQL-supporting shared hosting out there. > I seems to me, that if you are using shared hosting, and if your > database needs are modest, Sqlite3 might be the best choice. Especially > when Python 2.5 becomes more standard on shared hosting. I wouldn't use SQLite for any significant amount of multiprocess usage. It's good for monoprocess usage, though. (Multithreading is right out anyway.) > Has anybody had any particular difficulties with MySQL? Lots of them; don't use it. MySQL-PostgreSQL comparison http://www.teknico.net/devel/myvspg/index.en.html -- Nicola Larosa - http://www.tekNico.net/ You do have an automated test suite, right? And it does run periodically (daily or upon every check-in) in a continuous integration system, right? And you have everything set up so that you're notified by email or RSS feeds when something fails, right? And you fix failures quickly so that everything turns back to green, because you know that too much red, too often, leads to broken windows and bit rot, right? -- Grig Gheorghiu, February 2007 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
