#24040: _meta.db_table malformed in SQL statement when >31char
-------------------------------------+-------------------------------------
Reporter: JorisBenschop | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* status: new => closed
* resolution: => invalid
Comment:
Unless I've missed something, hashing only creates a problem when you are
integrating with a legacy database. If your tables are generated by
Django, there should be no problems.
I don't think we are going to abandon our current solution due to
backwards compatibility and the fact that it's advantageous for third-
party apps with long identifiers where you can't set `db_table` manually.
If you have other ideas or if I've missed something, please reopen.
--
Ticket URL: <https://code.djangoproject.com/ticket/24040#comment:6>
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/071.b84183c695aa5aa22d78484aa2bb80f6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
