Raphael Gaschignard

@BertrandBordage well, you can customize the through model in `TaggableManager` and just show up with another tag model entirely (that just follows a similar API, but might back the name...

> SELECT DISTINCT "taggit_tag"."id", "tests_taggedcustompk"."id" FROM "taggit_tag" INNER JOIN "tests_taggedcustompk" ON ("taggit_tag"."id" = "tests_taggedcustompk"."tag_id") INNER JOIN "django_content_type" ON ("tests_taggedcustompk"."content_type_id" = "django_content_type"."id") WHERE ("django_content_type"."app_label" = 'tests' AND "django_content_type"."model" = 'custompkfood') ORDER...

> Looking at the docs, it appears that the tags.all() queryset should maintain the ordering of the tags as they were initially set. did you see that anywhere? Or is...

When you're generating mgirations, a migration ends up being put inside the `taggit` package. This is because in your meta you have: ``` class Meta: verbose_name = _("news_tag") verbose_name_plural =...

Alright, we should add something to the FAQ about this (and for other things). subclassing models can easily mess things up if you're not careful

I haven't tried this but I believe that doing `Message.objects.filter(tags__name="tag1").filter(tags__name="tag2")` should give you what you want. That should return your messages that include `tag1`.... that are then filtered down by...

@mirodil1 do you have a full stack trace for these errors? this is not enough information for us to figure things out.

@naskio do you have a longer stack trace? please post more details.

@naskio thank you very much for that detail! It sounds very important. If in your system you have that problem, the easiest thing to do would be to normalize manually...

Good first issue: catching `MultipleObjectsReturned` and rethrowing it with a better error message to handle this.