I have a quick 'Opinion Poll' question regarding how to use Postgres with Django. I'm set up over at Rimu Hosting [http://www.rimuhosting.com/] and I'm going to have my first 'client' up and running soon.
I have my own site running against Postgres, plus I'll be installing some demo sites that will access Postgres. The client site will need a database as well. My question to the Django crowd is, "How would you manage the Postgres database(s) for multiple projects?" I'm thinking I'll have one (1) production database (prod) with each project under it's own schema and role (e.g., 'polls_schema' and 'polls_role'). I will also have a 'dev' and a 'stage' database installed locally for development. Would it make more sense, be more logical, cost more memory, etc., to have a separate database for each project? so there would be a prod_polls, prod_foo, etc? I was hoping some of you with real world experience with this kind of thing might be willing to share some pearls. In my code monkey day job the Oracle admins break things up in the former method, a database per 'environment'. However, I've read posts here before of people claiming to /never/ use postgres schemas. I interpret that to mean that having multiple databases in a cluster does not cost much... Remember, if you have an opinion you'd like to share, I'm interested in reading it! Thanks! Doug Van Horn May Digital Solutions http://www.maydigital.com/ [in progress] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
