[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (CMIS-655) Folder Children (restrictacceptable values for OrderBy)
[ http://tools.oasis-open.org/issues/browse/CMIS-655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Florian Mueller updated CMIS-655:
---------------------------------
Fix Version/s: V1.1
(was: V1.0 Errata)
Assignee: (was: Ethan Gur-esh)
> Folder Children (restrict acceptable values for OrderBy)
> --------------------------------------------------------
>
> Key: CMIS-655
> URL: http://tools.oasis-open.org/issues/browse/CMIS-655
> Project: OASIS Content Management Interoperability Services (CMIS) TC
> Issue Type: Improvement
> Components: Domain Model
> Affects Versions: Committee Draft 06
> Environment: n/a
> Reporter: Jay Brown
> Priority: Minor
> Fix For: V1.1
>
>
> Since folder getChildren is basically a specialized query against two different tables, supporting all orderBy values for all possible orderable properties becomes prohibitively difficult for some repositories.
> In some repositories, the underlying query against all documents (and sub classes of document) may not permit sorting by a field that only may be present on a subclass of document. But the scope of this call implies all cmis:document subclasses and all cmis:folder subclasses.
> An example of a case that may be difficult to correctly service is the following:
> A subclass of cmis:document named invoicedoc exists that has a an orderable property value of 'foo'.
> A folder getchildren is then reqested for a folder with an orderBy parm set to "foo".
--
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]