[OASIS Issue Tracker] Commented: (CMIS-269) SCORE() may need a wayto specify to which CONTAINS() predicate it applies

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12409#action_12409 ] 

Al Brown commented on CMIS-269:
-------------------------------

closed per creator's request

> SCORE() may need a way to specify to which CONTAINS() predicate it applies
> --------------------------------------------------------------------------
>
>                 Key: CMIS-269
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-269
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.61
>            Reporter: Florent Guillaume
>            Assignee: Ethan Gur-esh
>            Priority: Minor
>
> If a query with a JOIN has several CONTAINS() predicates, then there's no way for the SCORE() predicate to specify to which it refers.
> For instance in:
>   SELECT * FROM Document doc JOIN Document comment ON comment.docid = doc.objectid WHERE CONTAINS(doc, "foo") AND CONTAINS(comment, "bar") AND SCORE() > 0.5
> we don't know if the score applies to the "foo" match or the "bar" match.
> We can't just allow a <qualifer> in the SCORE() predicate because it will still be ambiguous when self-JOINs (like in the example above) are used.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira