#13245: manually set db_table should not validate if it needs to be truncated
-------------------------------------+-------------------------------------
Reporter: skoom | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: oracle | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by timo):
* easy: 1 => 0
Comment:
Hi Shai, I looked into this on PostgreSQL. Specifying `db_name="string
longer ... than 63 characters"` results in the table name being silently
truncated at 63 characters (does not use
`django.db.backends.utils.truncate_name`). Arguably this should be fixed,
perhaps there's already a ticket, although it seems quite uncommon and low
priority.
The action item I was proposing for this ticket was what Russ proposed in
comment 2: "I would expect to see a validation error if you ever tried to
synchronize a model with a db_table specification that exceeded the limits
of the backend."
Do you disagree with that? Of course, this ticket seems a bit trickier
than I expected given the Oracle specific logic in it's definition of
`quote_name` you mentioned regarding a quoted `db_name`.
--
Ticket URL: <https://code.djangoproject.com/ticket/13245#comment:10>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.b288997e35f415441d45fee13794a61b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
