[
https://issues.apache.org/jira/browse/ROL-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750630#comment-13750630
]
Glen Mazza commented on ROL-1755:
---------------------------------
Are you sure that union is not correct (or at least not an acceptable
interpretation) in this case? I want to know what someone has to say about
movies, I'll do tags/movies, about music I'll do tags/music, about both I'll do
tags/music+movies (so I won't have to get article duplication if I do separate
queries). Why would I be interested only in articles discussing *both* music
and movies--why would an article covering just one of the two not be useful for
me to see? If we used intersection, a blog article spending 2 paragraphs on
music and 2 paragraphs on movies would be useful for me, but if the author
splits that into two blog entries containing two paragraphs apiece, *neither*
blog article would be useful for me--which doesn't make sense. I think an
intersection could be better handled via a search instead of a tag URL.
> Tag intersection not an intersection
> ------------------------------------
>
> Key: ROL-1755
> URL: https://issues.apache.org/jira/browse/ROL-1755
> Project: Roller
> Issue Type: Bug
> Components: JPA Backend
> Reporter: David Johnson
> Assignee: David Johnson
> Priority: Minor
>
> Links like this http://host/blogname/tags/history+hypertext should give the
> intersection of the two tags history and hypertext, not the union. This is a
> regression caused by a bug in the JPA implementation used in 4.0.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
