So, till now I added "matches" to api and RDF implementations. The other ones I left them out as can be expressed using the current api. Still, not decided about the ManyAssociation api: * the isEmpty and isNotEmpty I can support them via isNull/isNotNull if I will allow also ManyAssociation (right now only Properties/Associations are supported), but the isEmpty/isNotEmpty looks to me like they express better the intent. * shall we implement "contains"?
Actually, about the isNull/isNotNull: are the names okay or isBound/isNotBound will be a better name for them? - this names are coming for the way they are named in SPARQL. Alin On Fri, Apr 11, 2008 at 12:32 PM, Alin Dreghiciu <[EMAIL PROTECTED]> wrote: > Hy guys, > > In the past weeks I was working on the query api/spi and RDF > implementation of spi. > Right now the query api allows the following: > > * and/or/not > * equals: Property = value > * greater than: Property > value > * greater or equal: Property >= value > * less than: Property < value > * less or equal: Property <= value > * isNull: Property or Association is not set > * isNotNull: Property or Association is set > > My question is: what other filtering predicates do you see as useful? > Right now I also see, but I would like to know if you find them useful: > > * matches: Property<String> matches a regexp. Or shall we call it "LIKE"? > * in: Property<T> in (T...) = evaluates to true when property value is > any of the values in array > * between: Property >= minValue && Property <= maxValue > > Also, till now there is no support for ManyAssociation(s). Question is > what kind of filtering shall we support for ManyAssociation(s)? > This can be useful 9yet I do not know how easy can be implemented): > > * isEmpty, isNotEmpty > * sizeEq, sizeNotEq, sizeGe, sizeGt, sizeLe, sizeLt > * contains: ManyAssociation collection contains a certain entity > > Cheers, > Alin > _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
