[OASIS Issue Tracker] (CMIS-768) Simplify CMIS query

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

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

Andy Hind edited comment on CMIS-768 at 4/7/14 7:36 PM:
--------------------------------------------------------

In regard to returning heterogeneous objects, I understand some repositories may not support this.
The 1.1 specification may already allow this. Documents and folders can have secondary types, so

SELECT * from some:secondaryType

may already return heterogeneous objects.

It is not clear as 2.1.14.2 seems to imply any virtual table name can be used. The BNF only allows primary types in from and join clauses.

This requires further consideration for V1.1 and has been raised as CMIS-771


was (Author: andy.hind):
In regard to returning heterogeneous objects, I understand some repositories may not support this.
The 1.1 specification may already allow this. Documents and folders can have secondary types, so

SELECT * from some:secondaryType

may already return heterogeneous objects.

It is not clear as 2.1.14.2 seems to imply any virtual table name can be used. The BNF only allows primary types in from and join clauses.

> Simplify CMIS query
> -------------------
>
>                 Key: CMIS-768
>                 URL: https://tools.oasis-open.org/issues/browse/CMIS-768
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Domain Model
>    Affects Versions: Proposals for 2.0
>            Reporter: Andy Hind
>
> This follows on from CMIS-758 where some discussion took place related to query and over lap with bulk get.
> There are 3 main issues with CMIS query that I see:
> 1) Now that we have secondary types, joining to all the secondary types you may wish to use is cumbersome
>      You also have to left outer join to any specific sub-types for which you may want properties.
> 2) To batch fetch all properties as part of a query requires that you know before hand what secondary types are applied to build the complex query above
>      While it may be possible to get the ids and use the new batch operations it would be good to get all you want in one shot.
> 3)  To get heterogeneous objects may require several calls for folders, documents, items
>      (I am not sure if we have considered selecting a secondary type and then outer joining to the base types - I would like to make that easy too) 
> An example use case for both would be to generate a dynamic folder/view of documents and folders defined by a query.
> To support this the query would have similar requirements to listing children of a folder. 



--
This message was sent by Atlassian JIRA
(v6.1.1#6155)