OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

Jay Brown commented on CMIS-758:
--------------------------------

Based on the discussion so far this [1] is how I am seeing the new command (going with FETCH as the name for now but that can change)  in a typical scenario where the user is trying to retrieve objects just created/modified in a batch. 

(as Florian said earlier) If the PROPERTIES part is missing, all properties are returned. If the PROPERTIES part is present, only the properties in the list are returned. If a property doesn't exist for an object, it is ignored.  
The WHERE clause would only be able to operate on the 9 properties that are common to all CMIS objects.  (comments on this?)

In the use case I am trying to cover here there is no need for a FROM.  Andy,  can you add a similar example (to [1] ) of what the FETCH line would look like in your use cases?

[1] FETCH  'id1', 'id2', 'id3', 'idn' PROPERTIES cmis:name, cmis:objectId, cmis:lastModificationDate, cmis:createdBy WHERE cmis:lastModificationDate > TIMESTAMP '2013-01-01T12:00:01.000Z'


> 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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]