We are in the process of moving an existing webapp/database to django. One of the features of our existing setup is the ability to have a command line tool post data from a remote client to a production version of our database for all to see or post to a test database for personal/informal consumption.
We're planning on starting with 0.96 django and I'm looking for a workaround to the one DB per project design. The command line tool for submitting data to the DB is using the django model and api. To match our previous design we would need multiple databases with the same schema with just different database names. Now my question. Is there an easy way to change the database settings dynamically? Ideally I'd like to parse the url and call a view function with the appropriate database settings. This would allow us to host one webapp for both DB's. I'd also like our command line tool to grab the DB name from the args and pass it to the django settings for the model. If there's no easy way to do this the only idea I've had is to host two versions of the project on the same web server with different DB settings. We could then wrap the command line tool with a sed script to edit the setting.py file on a remote client using the tool before submitting data to the server. Any feedback is appreciated. Cheers, -Brian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
