That sounds really interesting. Do you mean to create table (SQL DDL) in db schema? Or do you define new type e.g. PropertyList (key,value), and create objects with that type and then relationship between document and that type?
Thanks Krzysztof On 2017-10-11 18:24, "Suhaib Fahad" <fahad.suh...@pogeyan.com> wrote: > Secondary types are not helpful in querying with the use-case you have > specified, It looks like you need a 'cmis:relationship' between two types > like a Master-Detail table in DBs, and the Detail table will have Key/Value > pairs (for the dynamic field data) that you would use to specify a JOIN and > filter from. > > Not many repositories support joins in query yet, so could work around it > with querying twice. > > Thanks, > Fahad > > -----Original Message----- > From: krzysztoffzielin...@gmail.com [mailto:krzysztoffzielin...@gmail.com] > Sent: Wednesday, October 11, 2017 9:58 PM > To: dev@chemistry.apache.org > Subject: Re: RE: Secondary Type example from opencmis doc throws type > unknown error > > Thanks for reply. > > The question would be how should i name these properties, since they are not > known upfront? They are derived from client input. > > I have an idea to define a secondary type with two properties: key and > value. and store my dynamic property there. > > Is it possible to store a list/bag/array of secondary properties of the same > type, as opposed to storing just one? > > would i be able to specify cmis query that would check if the document has > the secondary property in the collection with given key and value? > > Thanks > Krzysztof > > On 2017-10-11 17:11, "Suhaib Fahad" <fahad.suh...@pogeyan.com> wrote: > > Could you inherit from "cmis:document" as base type and define custom > > properties in your custom type? That should give you the flexibility > > to use files + custom key-value pairs. > > > > Thanks, > > Fahad > > > > -----Original Message----- > > From: krzysztoffzielin...@gmail.com > > [mailto:krzysztoffzielin...@gmail.com] > > Sent: Wednesday, October 11, 2017 9:15 PM > > To: dev@chemistry.apache.org > > Subject: Re: Secondary Type example from opencmis doc throws type > > unknown error > > > > Is there another way of storing key-value pairs on documents that are > > not known upfront? i.e. to store a property that was not defined before? > > > > Krzysztof > > > > On 2017-10-11 16:39, Jeff Potts <jeffpott...@gmail.com> wrote: > > > They are not dynamic. A secondary type must already be known by the > > > repository before it can be applied. > > > > > > Some repositories support using CMIS to add type and secondary type > > > definitions to the repository. Once the repository registers your > > > definition you can then use it. But you cannot simply make up a > > > content model and start using it without registering it first, > > > otherwise you will get type unknown errors, as you have seen. > > > > > > Jeff > > > > > > On Wed, Oct 11, 2017 at 10:15 AM, krzysztoffzielin...@gmail.com < > > > krzysztoffzielin...@gmail.com> wrote: > > > > > > > Hello All, > > > > I was wondering how the secondary type work. They are meant to be > > > > dynamic, so when you should be able to create them on the fly. > > > > however, when i run example from the docs, i get > > > > > > > > CmisObjectNotFoundException: Type 'custom:classifictaion' is unknown! > > > > > > > > do you need to predefine the "custom" namespace? > > > > > > > > Thanks a lot > > > > Krzysztof > > > > > > > > > > > > >
