My own usage was just that 'a tag is a tag', where yours seem to have distinct types or classes of tags (location or language).
If those are not editable by a user, then I could see managing the UI presentation of the tags so they could be separated. If they really are your tags, you can build the logic to know what is what (with two types, you only have to keep track of half the tags -- if not type A then type B). You could use this knowledge to separate the tags for UI presentation and simply (re)combine them for persistence. Taht would let you leverage the tagging portion of has_many_polymorphs. Of course, that notion falls apart if the users can add their own tags. -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
