[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=35939#action_35939 ] 

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

Supporting a WHERE clause will allow a query like construction that can return heterogeneous objects.

I have been asked questions where CMIS clients want to find objects using SELECT and pull back arbitrary properties.
In 1.1 they have to 
1) do lots of JOINs
    a) JOIN many secondary types to pull back what they want; and/or
    b) LEFT OUTER  JOIN on to a sub-type (if this join type is supported); or
2) execute the queries, collect up all the IDs and then go get them

They want to treat all secondary type and sub-type properties as optional properties on an optional type.
They do not want to generate many joins as in case 1a) and can only do case 1b) on repositories that support this. 
Case 2) potentially involves several queries and one bulk fetch operations which we can make one call in many cases.

Using a query to define a "dynamic folder" is one use case.
Here clients want the same options that listing children of a real folder allows.

We could keep much the same syntax as select but allow any column selection and make FROM optional.
A type/secondary-type constraint(s) may be required and if present allows A.* style syntax to reduce the size of the select list

I would also suggest GET or FETCH in place of RETRIEVE as they are shorter and easier to spell.

> 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