← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Commented: (CMIS-179) Clarify behavior for arepository which may not be able to support the entire query grammar.

From
OASIS Issues Tracker <>
Date
2009-05-08T21:21:30+00:00
ID
526824652.1241817690267.JavaMail.tomcat55@mw00
Thread
[OASIS Issue Tracker] Commented: (CMIS-179) Clarify behavior for arepository which may not be able to support the entire query grammar.
[ http://tools.oasis-open.org/issues/browse/CMIS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10632#action_10632 ] 

Al Brown commented on CMIS-179:
-------------------------------

Good point.  I would suggest best attempt or throw exception.

> Clarify behavior for a repository which may not be able to support the entire query grammar.
> --------------------------------------------------------------------------------------------
>
>                 Key: CMIS-179
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-179
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: Draft 0.61
>            Reporter: Ryan McVeigh
>            Assignee: Ethan Gur-esh
>
> What are we supposed to do if our repo can't support part of the CMIS-SQL string? (e.g. we don't support a particular predicate, like UPPER(), LOWER() or pieces of ANY.) Do we throw an exception? Return no results? Return best attempt at results (which then may not strictly map)?

-- 
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
← Prev in month ← Prev in thread
Next in thread → Next in month →