id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
34423	Migrations, UniqueConstraint lenght of identifier can be too long for Postgres/MySQL	Joel Shapiro	nobody	"When creating a new unique constraint it is quite easy with the interpolation of %(class)s to generate a very long name as identifier (name) of the constraint.

Postgres and MySQL both have limits on how long the name can be (63/64) characters, Postgres does allow for a longer name but it will be truncated.

Creating two names with the same first part will make it so that we have two identical identifiers and the migrations will not work.

An error like this will be thrown;


{{{
django.db.utils.ProgrammingError: relation ""xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"" already exists
}}}
"	Cleanup/optimization	closed	Migrations	4.1	Normal	wontfix	migrations, unique_constraint, UniqeConstraint		Unreviewed	0	0	0	0	0	0