On 5/4/06, Kumar McMillan <[EMAIL PROTECTED]> wrote: > > Hi, I'm still new to django and have googled high and low for a way to > use a single dsn in the settings file instead of DATABASE_HOST, > DATABASE_USER, DATABASE_NAME, etc. No metion of it. Is there built > in support for this that I'm missing?
You're not missing anything, it's not there :) > If not, I am happy to submit a patch. What is the best place in svn > to patch against? Magic removal branch or trunk? The magic-removal branch was merged a few days ago, so it *is* the trunk now. > If you're asking why, here is a common situation I have with database > configurations... In order to run in multiple environments I declare > DSNs as environment variables so that this detail is decoupled from > the code. This also lets multiple users set up dev environments > easily and keeps sensitive information out of the code repository. As > it works now, it would be cumbersome to deal with 6 separate env vars: > engine, name, user, password, host, port. Sounds like a good idea to me. A patch would be great! Joseph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
