#13528: db_table truncation is applied based on the properties of the default
database
---------------------------------------------------+------------------------
Reporter: russellm | Owner:
andrewgodwin
Status: assigned | Milestone: 1.3
Component: Database layer (models, ORM) | Version: 1.2-beta
Resolution: | Keywords:
Stage: Accepted | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by andrewgodwin):
* owner: nobody => andrewgodwin
* status: new => assigned
Comment:
I'm working on this - my proposed solution is thus:
- Deprecate Options.db_table (PendingDeprecationWarning for 1.3)
- Add Options.get_db_table(using=db_alias)
- Change all the places Django uses db_table to use get_db_table
This should both solve the problem, and allow third-party apps to continue
using db_table (as it's still valid if you've only got one database).
--
Ticket URL: <http://code.djangoproject.com/ticket/13528#comment:5>
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
