#15131: pg_service.conf support
---------------------------------------------------+------------------------
Reporter: valczir.darkv...@gmail.com | Owner: nobody
Status: closed | Milestone:
Component: Database layer (models, ORM) | Version: 1.2
Resolution: wontfix | Keywords:
postgresql, pg_service, pg_service.conf
Stage: Unreviewed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by russellm):
* status: new => closed
* needs_better_patch: => 0
* resolution: => wontfix
* needs_tests: => 0
* needs_docs: => 0
Comment:
I'm not sure I see the benefit here. It's certainly nice that Postgres
provides a way to perform the abstraction that you describe, but I'm not
sure I see the advantage that is gained by having Django support it. It
would be a configuration scheme that only works for Postgres -- no other
backend (that I'm aware of) has an analogous configuration scheme. This
means that the cross-database nature of Django would be somewhat
compromised -- we would have a DATABASES setting that only works for
Postgres.
Closing wontfix; please start a discussion on django-dev if you feel
strongly about this.
--
Ticket URL: <http://code.djangoproject.com/ticket/15131#comment:1>
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-updates@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.
