Hi there,
I'm
working on JCRStore and QueryPlugin and I want to get some
feedback
> about
>
http://dev.xwiki.org/xwiki/bin/view/Design/XWiki+Query
+Language+Specification
>
> 1. Why our QueryPlugin's xpath isn't sufficient? (except it
> doesn't work
> now and some features are unimplemented :))
Actually, interestingly enough, after looking for a few secs at
xpath and
understanding a bit better how it works (thanks Wikipedia) I found
it easy
to understand. Provided users can find a treeview of how XWiki
underlying
elements work involved on
XWiki.org it could be easy to use...
In fact, rather than the query language itself I think the main
issue for
people starting to use XWiki is that it's hard to find what exactly
are the
XWiki elements (object, classes, etc) and how to build queries
around them.
Having various query languages is great because developers can use
the one
that they are the most familiar with. But for XWiki beginners what
is really
needed is a clear documentaiton page saying something like :
"If you want to query property A from object B in space C here are
the XWiki
bits involved :
- in hql : BaseObject, doc.web, prop.id.id (or whatever)
- in xpath : /*/*[space/Main/ and and obj/XWiki/XWikiUsers/
@xp:email like
'XXX']"
providing examples, explanations, and so on... As a XWiki beginner I
don't
even know what a query language is, yet I may want to build
applications ->
I need to know how I should go about doing this.
Having an automated query builder might be the best
answer to this
issue
though...
2. Are we sure to use sql-like query language?
I think sql isn't user friendly language.
For me XPath is way more clear and logical than SQL like language
but
I agree that only programmer can think that way ;)
Not necessarily ;-)
Guillaume