brj 2005/12/01 14:00:10
Modified: src/doc/forrest/src/documentation/content/xdocs/docu/guides
Tag: OJB_1_0_RELEASE query.xml
Log:
doc setPathOuterJoin()
Revision Changes Path
No revision
No revision
1.1.2.3 +11 -3
db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/query.xml
Index: query.xml
===================================================================
RCS file:
/home/cvs/db-ojb/src/doc/forrest/src/documentation/content/xdocs/docu/guides/query.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- query.xml 24 Mar 2005 17:54:17 -0000 1.1.2.2
+++ query.xml 1 Dec 2005 22:00:10 -0000 1.1.2.3
@@ -381,7 +381,7 @@
But you can force the SQLGenerator to use outer joins where
you find it useful.
<br/>
This is done by the method
- <em>QueryByCriteria#setPathOuterJoin(String)</em>.
+ <em>QueryByCriteria#setPathOuterJoin(String)</em>.
</p>
<source><![CDATA[
ReportQueryByCriteria query;
@@ -401,6 +401,14 @@
<p>
The first query will use an inner join for relationship
"konti", the second an outer join.
</p>
+ <p>
+ The whole path is evaluated, thus for a multi segment path (ie.
owner.address) you'll
+ have to set an outer join path for each segment that needs an
outer join.
+ <br/>
+ Given 'Account' - 'Owner' - 'Adress' and a query looking for
'Account'.
+ To force an outer join from 'Owner' to 'Adress'
setPathOuterJoin('owner.address') does the trick.
+ In case you also need an outer join between 'Account' and
'Owner' an additional setPathOuterJoin('owner') is needed.
+ </p>
</section>
@@ -767,4 +775,4 @@
<title>JDO queries</title>
</section>
</body>
-</document>
\ No newline at end of file
+</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
