The answer is not jumping out at me, so I'm going to post it here in case its a simple answer.
I want to access an existing DB on a remote server using Postgres. My boss is not crazy about having Django "polluting" this existing - large - db with its internal guts. But I don't see how to specify a SECOND db connection in Django. There is only one Settings.py file. Can I instantiate a second connector? And will doing so allow me to take advantage of the admin interface? Or, if I make my own connection, and use Django's db models (assuming I can even do that without conflict) will I still be able to "comfortably" program the Django way? Or maybe if I make a second connection, it has to be all by hand - using my own classes. No tie-in to Django's niceties..... Or is this a "deal breaker"? Where Django really only works if all "application" data is in the same db as all "site" data? Thanks in Advance! Richard Cooke Turnkey Automation Inc. --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
