#2257: [patch] syncdb should generate unique constraint names with hashes
-----------------------------+----------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: mtredinnick
Type: defect | Status: closed
Priority: normal | Milestone:
Component: django-admin.py | Version:
Severity: normal | Resolution: fixed
Keywords: |
-----------------------------+----------------------------------------------
Comment (by mtredinnick):
Thanks for the patch, Bill, but I ended up going with a hash of the table
names at the end, just to save a few characters.
For people reading this in the future, the reason I am not just punting
this and using no name so that MySQL can make on up is because it makes
debugging a little easier to see a constraint name that makes sense when
you violate it. It's worth a little pain to try and get that right.
--
Ticket URL: <http://code.djangoproject.com/ticket/2257>
Django <http://code.djangoproject.org/>
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 django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates
-~----------~----~----~----~------~----~------~--~---
