#13053: Support for non-static DB connection info
---------------------------------------------------+------------------------
Reporter: Lynge | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Someday/Maybe | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by Lynge):
And now, 8 months later, I finally get around to looking at it.
I am submitting a draft for, what I have called, ActiveSettings
This is just meant to be a hook that will let external projects get a
chance to change the settings as they are being requested.
If this, or something like it, could be implemented, then I can just
construct an external project that will let people solve this problem of
sharding costumers and without getting in the way of anyone that will not
be needing it, which I suspect is the largest part of the Django user-
base.
The diff is just a draft since this is my first contribution to Django, I
thought I would post it for scrutiny before doing the docs and tests. I am
sure there is a lot of errors in it, but the idea should be clear.
Also, should I be taking this up on the mailing list? I read something
about that in the contribution guide.
--
Ticket URL: <http://code.djangoproject.com/ticket/13053#comment:3>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
