Jérémi:
Aha! I should have read my mail before sending my last note, which I began composing last
night. That clears a lot of the mystery. I will save my other questions until after
I've read your reference; thank you.
But it re-raises for me the issue I had thought resolved - that of where the boundary of
queryability may be. I had assumed that it was the same as the boundary of the
XWiki-defined object model, as it would seem logically if it had to be supported as a
database map, but since it's a general-purpose persistence tool, might that assumption
be wrong? Probably, any queryable object would have to be modeled in the database, but
it's a grey area in my understanding. I do note that date fields are returned as
java.sql.Timestamp rather than as java.util.Date, in case that has any bearing on the
matter.
brain[sic]
-----Original Message-----
From: jeremi joslin [mailto:jeremi23@gmail.com]
Sent: Thursday, March 23, 2006 10:47 PM
To: xwiki-users(a)objectweb.org
Subject: Re: [xwiki-users] SQL hair-pulling
On 3/24/06, THOMAS, BRIAN M (SBCSI) <bt0008(a)att.com> wrote:
As mentioned in an earlier message, I got into the
$xwiki.search()
world yesterday, and am thoroughly confused.
The main problem seems to be that the XWiki database schema and the
schema used in all of the $xwiki.search() queries I have found are
completely disjoint.
Instead of the documented tables and columns, what seems to be used is
a schema which reflects the object model within XWiki. This would
really be convenient if true; is it?
Hi,
Yes, XWiki is using hibernate for the database mapping. So it's not a sql query, but
a hql query. You use the objects and members name to make the request. (if you don't
know the hql, you can take a look to the hibernate documentation :
http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#queryhql)
Jérémi
--
Blog:
http://www.jeremi.info
LinkedIn:
https://www.linkedin.com/profile?viewProfile=&key=1437724
Project Manager XWiki:
http://www.xwiki.org
skype: jeremi23 -- msn et gtalk : jeremi23(a)gmail.com