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
23498	V1.7 migration doesn't properly rebuild the through table from 3rd party library	James Lin	nobody	"This is not necessarily a bug but would be great to have this working:

I recently installed https://github.com/adsworth/django-onetomany which adds an unique constraint in the through table, UNIQUE KEY `referenceitem_id` (`referenceitem_id`), see below:


{{{
| accounts_transaction_references | CREATE TABLE `accounts_transaction_references` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `transaction_id` int(11) NOT NULL,
  `referenceitem_id` int(11) NOT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `referenceitem_id` (`referenceitem_id`),
  KEY `accounts_transaction_references_f847de52` (`transaction_id`),
  KEY `accounts_transaction_references_11805749` (`referenceitem_id`),
  CONSTRAINT `a_referenceitem_id_179ed3a0a0b94838_fk_accounts_referenceitem_id` FOREIGN KEY (`referenceitem_id`) REFERENCES `accounts_referenceitem` (`id`),
  CONSTRAINT `accou_transaction_id_7dafd9eb9684568c_fk_accounts_transaction_id` FOREIGN KEY (`transaction_id`) REFERENCES `accounts_transaction` (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=12 DEFAULT CHARSET=latin1 |
}}}

Then I reverted to the standard ManyToManyField, ran the migration, but the unique constrain didn't get removed."	Uncategorized	closed	Migrations	1.7	Normal	invalid			Unreviewed	0	0	0	0	0	0