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
24954	Adding an explicit UUID id doesn't change type of ManyToMany fields pointing to it	cloudOver	nobody	"I have models with manyToMany field and uuid based primary keys, e.g.:

{{{
class SomeModel(models.Model):
    id = models.UUIDField(primary_key=True, default=uuid.uuid4, editable=False)
    blockers = models.ManyToManyField('self', symmetrical=False, blank=True)
    ....
}}}
In 1.8 django creates new table, which has integer-based identifier for ManyToMany relationship:
{{{
describe overCluster_somemodel_blockers;
+--------------+---------+------+-----+---------+----------------+
| Field        | Type    | Null | Key | Default | Extra          |
+--------------+---------+------+-----+---------+----------------+
| id           | int(11) | NO   | PRI | NULL    | auto_increment |
| from_somemodel_id | int(11) | NO   | MUL | NULL    |                |
| to_somemodel_id   | int(11) | NO   | MUL | NULL    |                |
+--------------+---------+------+-----+---------+----------------+
3 rows in set (0.00 sec)
}}}
Foreign fields from that additional table fails (integer field points to uuid fields). The same problem exists with string based id. I haven't found that bug in sqlite backend."	Bug	closed	Migrations	1.8	Normal	duplicate	ManyToMany, UUID		Accepted	0	0	0	0	0	0