> Yeah, that patch is then clearly broken :/ The unique_together part is
> correct. And I'm not sure why that should lead to *two* indexes on
> listid - that looks like a django bug, if that creation is purely from
> that model.
Indeed, this comes from the patch. Sending a fix on the original thread.
I'd appreciate a more complete review of the patch so that we can move on with it.
--
Célestin Matte
