You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by ol...@apache.org on 2003/10/21 14:03:31 UTC
cvs commit: db-ojb/xdocs query.xml
oliverm 2003/10/21 05:03:31
Modified: xdocs query.xml
Log:
minor typos (plural of issue and keyword)
Revision Changes Path
1.22 +2 -2 db-ojb/xdocs/query.xml
Index: query.xml
===================================================================
RCS file: /home/cvs/db-ojb/xdocs/query.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- query.xml 23 May 2003 17:00:36 -0000 1.21
+++ query.xml 21 Oct 2003 12:03:30 -0000 1.22
@@ -329,8 +329,8 @@
This feature allows to have <b>multiple</b> aliases for the same table. The standard behaviour of OJB is to build one alias for one relationship.
<br/><br/>
Suppose you have two classes Issue and Keyword and there is a 1:N relationship
-between them. Now you want to retrieve Issues's by querying on Keword's.
-Suppose you want to retrieve all Issue with keywords 'JOIN' and 'ALIAS'. If these values
+between them. Now you want to retrieve Issues by querying on Keywords.
+Suppose you want to retrieve all Issues with keywords 'JOIN' and 'ALIAS'. If these values
are stored in the attribute 'value' of Keyword, OJB generates a query that contains
" A1.value = 'JOIN' AND A1.value = 'ALIAS' " in the where-clause. Obviously,
this will not work, no hits will occur because A1.value can not have
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org