#12499: Allow a model's Meta to specify a single multi-db alias
------------------------------------------------------------+---------------
Reporter: crucialfelix <crucialfe...@gmail.com> | Owner:
nobody
Status: closed | Milestone:
1.2
Component: Database layer (models, ORM) | Version:
Resolution: wontfix | Keywords:
multi-db
Stage: Unreviewed | Has_patch: 0
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:
This feature was implemented in an early draft of multi-db, and
specifically removed. The database shouldn't be specified as a Meta
property - consider the case of reusable apps. If your model defines
Meta.connection (the original draft called it Meta.using), you can't share
that model with any other Django user without forcing your particular
database usage strategy.
--
Ticket URL: <http://code.djangoproject.com/ticket/12499#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-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.
