[OASIS Issue Tracker] Commented: (CMIS-758) Discussion of more powerful batch operations for next version

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

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

Andy Hind commented on CMIS-758:
--------------------------------

For the use cases I have described you do not know the IDs of the cmis objects.
The objects are to be found via query. 

It is possible to use SELECT. Several queries can return properties direct or the object ids and subsequently use the suggested FETCH.
CONS:
     This is at least two stages 
             Perhaps a query for folder sub-types and document subtypes - may be a merge if ordered - then a subsequent FETCH by ID
             or two complex queries to pull back the required property sets
     The queries may be complex  
             Left outer joins onto all the secondary types and sub-types for which you want to pull back properties  
             Requires support for Left outer join for "self" joins


It may be that a different relational view projection would solve this. Something like:

"The virtual table for a type P includes optional properties derived from all properties of all sub-types of type P and all secondary type properties that could be applied to type P" 
Secondary type virtual tables would have optional properties from ALL types (primary and secondary).
Still respecting the property/type definitions for queryable, orderable etc

We could also support an untyped query: 
SELECT *.:cm:name, *.an:other, ...  FROM * .... WHERE *.yetan:other = 'boo'

This would allow simpler queries that can optionally pull back properties from sub-types/secondary-types or use them in predicates or for ordering 

FIND could be used in place of SELECT to indicate this broader virtual table definition 

> Discussion of more powerful batch operations for next version
> -------------------------------------------------------------
>
>                 Key: CMIS-758
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-758
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: New Feature
>          Components: Domain Model
>    Affects Versions: Proposals for 2.0
>            Reporter: Jay Brown
>
> Creating this record as a placeholder for discussions on this subject. 
> What additional batch features should we support in v.next? (e.g.  batch Create, Delete, ...) 
> What should they look like? etc. 
> Please comment.

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