id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
1052	db.create_table  generates index name too long for mysql	fexcoffi@…	andrew	"Issue does not exist on 0.5:
CREATE INDEX `management_system_named_system_group_systems_namedsystemgroup_i` ON `management_system_named_system_group_systems` (`namedsystemgroup_id`)

On 0.73:
errorhandler
_mysql_exceptions.OperationalError: (1059, ""Identifier name 'management_system_named_system_group_systems_groupsysteminstance_id' is too long"")

django ran into similar issue in the past https://code.djangoproject.com/ticket/1820
I ran into that issue converting script from 0.5 with M2M:
        db.create_table('management_system_named_system_group_systems', (
                ('id', self.gf('django.db.models.fields.AutoField')(primary_key=True)),
                ('namedsystemgroup', self.gf('django.db.models.fields.related.ForeignKey')(NamedSystemGroup)),
                ('groupsysteminstance', self.gf('django.db.models.fields.related.ForeignKey')(GroupSystemInstance)),
                ))

when generating index name, it concatenates all the names - resulting in a name too long for mysql to handle.
I did a syncdb to see what django (1.1.4) did and it did not even bother generating an index, so no help there. As we are talking about index names here, I don't think we really care on the name as long as it is unique.... so maybe the hash suggestion in the django ticket might sufice."	defect	closed	trivial	The Future	commands	0.7.3	invalid