#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
------------------------------+---------------------------------------------
Changes (by mtredinnick):
* stage: Design decision needed => Accepted
Comment:
The whole auto-name-generation stuff is a bit fragile in this respect. We
spent ages last year fixing up index lengths. Oracle has similar problems,
so I keep meaning to look at the boulder-oracle-sprint branch and steal
some of those ideas. Need to talk over with Jacob how he wants to merge
all that stuff in, because in the medium-term (pre-1.0?) we should
abstract a lot of that into the backend.
For now, documenting it is a reasonable band-aid, but it's one of things I
want to look at prior to 1.0; just not sure if we'll have time (it's going
to be a slightly backwards-incompatible change, which is why I have that
target in mind).
--
Ticket URL: <http://code.djangoproject.com/ticket/1820#comment:4>
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
-~----------~----~----~----~------~----~------~--~---
