My issue with adding DSN support to Django isn't that its not useful to some people, but that it feels like we are adding functionality that belongs in the DB-API layer, not Django. In an ideal world, the database settings would just be passed verbatim to the connect() function of the appropriate DB backend. Unfortunately, this is the one function in DB-API that varies among providers so there is no standard syntax. Some implementations support a DSN argument and others don't.
It seems like for every objection to the current feature (reusing existing environment variables, supporting "standard" DSNs, securing passwords) there is a simple, reasonable solution, (albeit one that may require writing a few lines of code) yet some people don't find that satisfactory. There are lots of useful snippets on the Django project site that aren't part of the official distribution. Couldn't someone just post the parse_dsn code there and let it bake for a while? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers -~----------~----~----~----~------~----~------~--~---
