#13528: db_table truncation is applied based on the properties of the default
database
---------------------------------------------------+------------------------
Reporter: russellm | Owner: nobody
Status: new | 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 russellm):
* milestone: 1.2 => 1.3
Comment:
This isn't a trivial thing to fix, and it only affects users that have:
1. multiple databases
2. from different vendors
3. where the default database has a longer maximum allowed length than
the other vendors database.
4. and there are tables whose table names exceed the shorter max_length
5. and the db_table can't be renamed.
For example, if you have a PostgreSQL default database (max_length=64),
and an Oracle secondary database (max_length=30), and you can't keep your
table names to under 30 characters, you will be affected by this bug. This
is a sufficiently edge case problem that I'm going to bump from 1.2.
--
Ticket URL: <http://code.djangoproject.com/ticket/13528#comment:2>
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.
