[#CMIS-179] Clarify behavior for a repository which may not be able to support the entire query grammar.

OASIS Content Management Interoperability Services (CMIS) TC

Clarify behavior for a repository which may not be able to support the entire query grammar.

Created: 08/May/09 03:48 PM Updated: 11/Jan/10 06:41 PM

Component/s:

Domain Model

Affects Version/s:

Draft 0.61

Fix Version/s:

Draft 0.62

Proposal:

« Hide

throw NotSupported if a functionality in the query is not supported by underlying repository

Also - remove UPPER(), LOWER()

Description

« Hide

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)?

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Al Brown added a comment - 08/May/09 05:21 PM

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

[ Permalink | « Hide ]

Al Brown added a comment - 08/Jun/09 01:22 PM

deferred to query wg

[ Permalink | « Hide ]

Al Brown added a comment - 10/Jun/09 11:45 AM

throw NotSupported if a functionalityin the query is not supported by underlying repository

[ Permalink | « Hide ]

Al Brown added a comment - 15/Jun/09 11:36 AM

WG proposal

[ Permalink | « Hide ]

Al Brown added a comment - 19/Jun/09 06:00 PM

added to 62b

[ Permalink | « Hide ]

Al Brown added a comment - 04/Jan/10 11:40 PM

JIRA Cleanup