#9910: Allow to change db_table for django contrib apps
-----------------------------------+----------------------------------------
Reporter: zlw | Owner: nobody
Status: closed | Milestone:
Component: Contrib apps | Version: 1.0
Resolution: wontfix | Keywords: db_table, table name
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
-----------------------------------+----------------------------------------
Changes (by russellm):
* status: new => closed
* resolution: => wontfix
Comment:
First off, I'd question the wisdom of anyone that wants to put multiple
projects into a single database. However, even if I did accept the use
case, allowing piecemeal renaming of individual tables wouldn't be the
solution. A better approach would be something like #6148, which provides
for consistent schema namespacing. This way, you make one project level
setting, and all tables in the project inherit a common namespace.
--
Ticket URL: <http://code.djangoproject.com/ticket/9910#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-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
-~----------~----~----~----~------~----~------~--~---
