[OASIS Issue Tracker] (CMIS-771) Clarify the query support for secondary types

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

    [ https://issues.oasis-open.org/browse/CMIS-771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58544#comment-58544 ] 

David Choy commented on CMIS-771:
---------------------------------

Regarding the problem of "substantive change", a conservative alternative to Proposal 2A may be:

In v1.1 Errata, point out the error in the BNF and its inconsistency with the narrative. State that this bug will be fixed in v2.0. Suggest that v1.1 Client should not include any secondary type in a query.


> Clarify the query support for secondary types
> ---------------------------------------------
>
>                 Key: CMIS-771
>                 URL: https://issues.oasis-open.org/browse/CMIS-771
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Bug
>          Components: Domain Model
>    Affects Versions: V1.1 Errata
>            Reporter: Andy Hind
>            Priority: Critical
>
> The query support for secondary types is not clear.
> CMIS-742 defined the query behaviour for secondary types in CMIS 1.1.
> CMIS-742 and section  2.1.14.2 of the 1.1 specification imply that secondary types can be used alone.
> For example
> SELECT * from cmis:rm_hold
> There are two issues with this.
> 1) It implies that heterogeneous objects may be returned from a query, as the same secondary type could be applied to both documents and folders.  Heterogeneous object can not be returned for all repositories.
> 2) Section 2.1.14.2.1, BNF Grammar, allows only <table name> in both the <from clause> and <joined table>. <table name> is defined to identify a primary type. There is a <secondary type table name> defined but only used in <column reference>. It looks like this was overlooked in the changes made for CMIS-742. The current BNF implies that only primary types may appear in FROM and JOIN clauses.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)