#1820: Autogenerated ManyToMany fields can generate too long identifiers for
mysql
to handle
------------------------------+---------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: adrian
Status: new | Component: Database wrapper
Version: SVN | Resolution:
Keywords: mysql | Stage: Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------+---------------------------------------------
Comment (by mtredinnick):
We've more or less solved the constraint problem already (we try to keep
things a little bit readable to help with debugging, but there is a hash
involved). This particular ticket is talking about and auto-generated
table name, by the looks of it (which is a case we didn't previously look
at). I'm not in favour of just using hashes everywhere, because then we
are needlessly punishing people who use databases which don't have
unreasonably ridiculous identifier limitations and making their debugging
and manual work harder. Hence the plan to move a lot of the identifier
generation stuff into the respective backends so that databases like MySQL
and Oracle can be handled specially.
--
Ticket URL: <http://code.djangoproject.com/ticket/1820#comment:6>
Django Code <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
-~----------~----~----~----~------~----~------~--~---
