You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-user@db.apache.org by Matthias Laube <ml...@gmx.de> on 2003/06/25 11:32:42 UTC

More than one class in an OJB-OQL from clause?

Hi!

I don't have a really reliable OQL reference yet (anyone knows where to 
get it as the odmg.org site is down?) , but from what I know it is 
possible to have more than one class (with aliases) in the from clause 
although the result consists only of one target class. (as far as I know 
thats an OJB limitation). I only want the references to other classes to 
use them in the where clause (like a criteria for an attribute that is 
related with the target class by a m:n relation).

Is that yet possible with the OJB implemention of OQL or even with the 
PersistenceBroker API. I worked around it by using an sql Criteria but I 
don't find it optimal.

Thanks for help.
Matthias.


Re[2]: More than one class in an OJB-OQL from clause?

Posted by Alexander Prozor <ap...@isd.dp.ua>.
Hello Matthias,

Please provide example of such query :)))).
Please!!!

ML> Ok, I got it, was a newbie question,
ML> I couldn't imagine to query collection-attributes using the dot-notation.

ML> my feeling right now:
ML> OJB is such COOL tool.


-- 
Best regards,
 Alexander                            mailto:apro@isd.dp.ua


Re: More than one class in an OJB-OQL from clause?

Posted by Matthias Laube <ml...@gmx.de>.
Ok, I got it, was a newbie question,
I couldn't imagine to query collection-attributes using the dot-notation.

my feeling right now:
OJB is such COOL tool.

Matthias Laube wrote:

> Hi!
>
> I don't have a really reliable OQL reference yet (anyone knows where 
> to get it as the odmg.org site is down?) , but from what I know it is 
> possible to have more than one class (with aliases) in the from clause 
> although the result consists only of one target class. (as far as I 
> know thats an OJB limitation). I only want the references to other 
> classes to use them in the where clause (like a criteria for an 
> attribute that is related with the target class by a m:n relation).
>
> Is that yet possible with the OJB implemention of OQL or even with the 
> PersistenceBroker API. I worked around it by using an sql Criteria but 
> I don't find it optimal.
>
> Thanks for help.
> Matthias.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-user-help@db.apache.org
>
>