> Sure you can. You might want to look at sqlite, as it's the > easiest to set up. You can painlessly switch to a "better" > database engine when going to production, though sqlite does > quite well the job, even in production.
I second Christian's suggestion of using sqlite for its minimal-fuss configuration (the OS permissions for the web-server/django process on the database file are the permissions you get). It even has a ":memory:" database which is handy for testing purposes (never touching a file). I would add a small caveat to "painlessly": it's painless unless you try and monkey with the underlying SQL through either an extra() call or hacking the ORM, both of which I do far too regularly. If you mess with either of these more obscure corners of Django (okay, the extra() isn't obscured as it's right there in the docs, but not many folks seem to know about it or use it), you just have to be careful that your SQL is portable across the various servers you expect to support. However, if you avoid touching DB specific code, the Django ORM does a rather good job of abstracting most of this stuff away so your code becomes portable across DB engines. -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 -~----------~----~----~----~------~----~------~--~---
